RTEMS | cpukit: Use CONFIGURE_MAXIMUM_PRIORITY with EDF (!831)

[Joel Sherrill (@joel)]

Merge request https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831 was reviewed by Joel Sherrill

--
  
Joel Sherrill started a new discussion on testsuites/sptests/spedfsched05/init.c: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831#note_136054

 > +
 > +/*
 > + * Copyright (C) 2014, 2020 embedded brains GmbH & Co. KG

This appears to be a completely new file. Did you just copy it and, thus, the copyright is the same? Or did you copy and modify it? If the first, the file should be referenced, not copied. If the latter, you probably need to add yourself to the copyright.

--
  
Joel Sherrill started a new discussion on testsuites/sptests/spedfsched03/system.h: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831#note_136055

 >  #define CONFIGURE_MAXIMUM_TASKS               7
 >  #define CONFIGURE_MAXIMUM_PERIODS             10
 > +#define CONFIGURE_MAXIMUM_PRIORITY            512

Is there any guidance for picking this value? The confdefs.h check for being a power of 2 appears to be disabled for EDF and CBS. 

Is the default to still have 256 priority levels and EDF/CBS deadlines get worked into that?


-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/831
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20251117/f4fc104c/attachment.htm>