On 05/03/15 15:19, Gedare Bloom wrote:
OK. On a related note, I don't like this "MINIMUM" and "MAXIMUM"
terminology I'd prefer HIGHEST and LOWEST, are we stuck with MINIMUM
and MAXIMUM for API compatibility?
In the score files, we can name it as we like, but I am not sure if its
worth to spend
OK. On a related note, I don't like this "MINIMUM" and "MAXIMUM"
terminology I'd prefer HIGHEST and LOWEST, are we stuck with MINIMUM
and MAXIMUM for API compatibility?
On Thu, Mar 5, 2015 at 2:33 AM, Sebastian Huber
wrote:
> ---
> cpukit/rtems/src/timerserver.c | 2 +-
> cpukit/sco
---
cpukit/rtems/src/timerserver.c | 2 +-
cpukit/score/include/rtems/score/priority.h | 7 +++
cpukit/score/src/mpci.c | 2 +-
3 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/cpukit/rtems/src/timerserver.c b/cpukit/rtems/src/timerserver.c
index
