On 03/10/2019 07:44, Chris Johns wrote:
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?
The test would only use interrupts which are not connected to a peripheral.
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. :)
Every BSP needs to implement this function on their own.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
