Release | RTEMS Classic and POSIX mapping API (#15)

[Chris Johns (@chris)]

Chris Johns created an issue: https://gitlab.rtems.org/rtems/rtos/rtems-release/-/issues/15



## Summary

Applications using RTEMS can be a mix of POSIX and Classic threads. For example EPICS using RTEMS 5 and 6 is POSIX based however some parts of RTEMS require ClassiC thread priorities be used. EPICS provides is own priority mapping so that project needs to track the POSIX and Classic API priority maps to have a unified system. RTEMS provide no API to move priorities between mappings.

1. Provide mappings.
2. Detail any constraints using any priority mapping calls.

The discussion in the EPIC PR https://github.com/epics-base/epics-base/pull/575 highlights the issues.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems-release/-/issues/15
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/20250203/102c91c5/attachment.htm>