Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | score: Add per scheduler instance maximum priority | Sebastian Huber | 2016-05-20 | 1 | -1/+1 |
| | | | | | | | | | | | The priority values are only valid within a scheduler instance. Thus, the maximum priority value must be defined per scheduler instance. The first scheduler instance defines PRIORITY_MAXIMUM. This implies that RTEMS_MAXIMUM_PRIORITY and POSIX_SCHEDULER_MAXIMUM_PRIORITY are only valid for threads of the first scheduler instance. Further API/implementation changes are necessary to fix this. Update #2556. | ||||
* | Change all references of rtems.com to rtems.org. | Chris Johns | 2014-03-21 | 1 | -1/+1 |
| | |||||
* | posix: Create priority implementation header | Sebastian Huber | 2013-07-22 | 1 | -0/+120 |
Move implementation specific parts of priority.h and priority.inl into new header file priorityimpl.h. Remove priority.h since there is no application visible API. |