Matteo Concas commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1514#note_160113 Then all interrupt functions would only act on interrupt line 1. This is means disabling interrupt 5 would also disable interrupt 1 etc. This gets a bit confusing for users (although they should know they have this map already) when calls to `rtems_interrupt_entry_install()` for different interrupt lines will fail if you don't use `RTEMS_INTERRUPT_SHARED`. For example: ```c status = rtems_interrupt_entry_install(1, RTEMS_INTERRUPT_UNIQUE, isr1); // status = RTEMS_SUCCESSFUL status = rtems_interrupt_entry_install(5, RTEMS_INTERRUPT_UNIQUE, isr5); // status = RTEMS_RESOURCE_IN_USE ``` (I haven't played with this functionality in a bit but this is what I remember) -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/1514#note_160113 You're receiving this email because of your account on gitlab.rtems.org. Unsubscribe from this thread: https://gitlab.rtems.org/-/namespace/49/sent_notifications/5-5xj8zp3413luuhzf7rcmeq4ev-1d/unsubscribe | Manage all notifications: https://gitlab.rtems.org/-/profile/notifications | Help: https://gitlab.rtems.org/help
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
