Sebastian Huber commented: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5578#note_150389 Ok, I think we should clarify this in the documentation. The interrupt priorities should be like Classic API priorities starting at 0 up to a controller-specific maximum. Yes, the current validation test doesn't work on RISC-V. I have a couple of RISC-V patches in my queue. One of them fixes the issue with the `UINT32_MAX` being a valid interrupt priority. I work really hard to upstream everything, but it is a lot of work since almost everything is related to the pre-qualification work. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/issues/5578#note_150389 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
