diff options
| author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2008-12-14 18:31:43 +0000 |
|---|---|---|
| committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2008-12-14 18:31:43 +0000 |
| commit | a6608123c0952979821bbfe4bf58713403c2f9cb (patch) | |
| tree | 6f3206c34b4f75b3bc5146d9527f165cbc3c9205 /cpukit/posix/include/rtems/posix/priority.h | |
| parent | 2008-12-12 Joel Sherrill <joel.sherrill@OARcorp.com> (diff) | |
| download | rtems-a6608123c0952979821bbfe4bf58713403c2f9cb.tar.bz2 | |
2008-12-14 Joel Sherrill <joel.sherrill@oarcorp.com>
* itron/src/chg_pri.c, itron/src/cre_tsk.c, itron/src/rot_rdq.c,
posix/Makefile.am, posix/include/rtems/posix/mutex.h,
posix/include/rtems/posix/priority.h, posix/src/mutex.c,
score/include/rtems/score/priority.h: Run all tests successfully with
maxixum number of priorities as 16 instead of 256. This was done by
temporarily modifying the score priority.h maximum. This allowed
testing of all API code to ensure that it worked properly with a
reduced number of priorities. Most modifications were to switch from
hard-coded maximum to using the SuperCore variable based upon
configured number.
* posix/src/mutexdefaultattributes.c: Removed.
Diffstat (limited to '')
| -rw-r--r-- | cpukit/posix/include/rtems/posix/priority.h | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/cpukit/posix/include/rtems/posix/priority.h b/cpukit/posix/include/rtems/posix/priority.h index 14eb959950..2111bd3118 100644 --- a/cpukit/posix/include/rtems/posix/priority.h +++ b/cpukit/posix/include/rtems/posix/priority.h @@ -21,7 +21,7 @@ /* * 1003.1b-1993,2.2.2.80 definition of priority, p. 19 * - * "Numericallly higher values represent higher priorities." + * "Numerically higher values represent higher priorities." * * Thus, RTEMS Core has priorities run in the opposite sense of the POSIX API. * @@ -30,9 +30,12 @@ * because GNAT maps the lowest Ada task priority to the lowest thread * priority. The lowest priority Ada task should get to run, so there is * a fundamental conflict with having 255 priorities. + * + * But since RTEMS can be configured with fewer than 256 priorities, + * we use the internal constant. */ -#define POSIX_SCHEDULER_MAXIMUM_PRIORITY (254) +#define POSIX_SCHEDULER_MAXIMUM_PRIORITY (PRIORITY_MAXIMUM - 1) #define POSIX_SCHEDULER_MINIMUM_PRIORITY (1) |