On 2/10/19 5:28 pm, Sebastian Huber wrote: > the interrupt extension API implementation is already quite complex and not > covered by the test suite: > > https://git.rtems.org/rtems/tree/bsps/shared/irq > > In order to write generic tests for this we have to know which interrupt > vector > can be controlled by software.
Do I assume the testsuite's tests are for hard IP resources? One approach would be to add an > rtems_interrupt_get_capabilities() function: It would be nice to be able to add and remove entries based on soft IP that can be runtime loaded. :) Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
