RCS file: /usr1/CVS/rtems/cpukit/posix/inline/rtems/posix/priority.inl,v
retrieving revision 1.12
diff -u -r1.12 priority.inl
|
|
|
28 | 28 | * Thus, RTEMS Core has priorities run in the opposite sense of the POSIX API. |
29 | 29 | */ |
30 | 30 | |
31 | | RTEMS_INLINE_ROUTINE boolean _POSIX_Priority_Is_valid( |
| 31 | RTEMS_INLINE_ROUTINE bool _POSIX_Priority_Is_valid( |
32 | 32 | int priority |
33 | 33 | ) |
34 | 34 | { |
35 | | return (boolean) (priority >= 1 && priority <= 254); |
| 35 | return ((priority >= POSIX_SCHEDULER_MINIMUM_PRIORITY) && |
| 36 | (priority <= POSIX_SCHEDULER_MAXIMUM_PRIORITY)); |
36 | 37 | } |
37 | 38 | |
38 | 39 | RTEMS_INLINE_ROUTINE Priority_Control _POSIX_Priority_To_core( |
39 | 40 | int priority |
40 | 41 | ) |
41 | 42 | { |
42 | | return (Priority_Control) (255 - priority); |
| 43 | return (Priority_Control) (POSIX_SCHEDULER_MAXIMUM_PRIORITY - priority + 1); |
43 | 44 | } |
44 | 45 | |
45 | 46 | RTEMS_INLINE_ROUTINE int _POSIX_Priority_From_core( |
46 | 47 | Priority_Control priority |
47 | 48 | ) |
48 | 49 | { |
49 | | return 255 - priority; |
| 50 | return (POSIX_SCHEDULER_MAXIMUM_PRIORITY - priority + 1); |
50 | 51 | } |
51 | 52 | |
52 | 53 | #endif |