mirror of
https://gitlab.rtems.org/rtems/rtos/rtems.git
synced 2026-11-16 19:04:53 +08:00
The interrupt controller operations were not implemented. Every one of them returned RTEMS_UNSATISFIED, so ts-validation-intr reported 2511 failures, most of them because rtems_interrupt_vector_is_enabled() must work for every valid vector. Drive the controller of the TX3904. A source passes when its level in the interrupt level registers is greater than the level in the interrupt mask register, so the level is both the priority and the enable, and the vector numbers of the BSP are the source numbers of the controller. A bit of the interrupt status register reads as zero while its source is asserted. The two software interrupts of the processor are raised and cleared in the cause register and are the only sources this board can raise. The sources which do not pass the controller are masked in the status register, which the context of every thread enables completely, so they report as enabled and nothing disables them. The other BSPs of the architecture keep the operations which are not implemented, now in their own file. Thirteen failures remain. They need a vector which the validation tests can raise and also enable and disable, and this board has none: the status register belongs to the context of a thread, so a disable of a software interrupt would not survive a context switch. Update #5688. Assisted-by: Claude:claude-opus-5 claude-code Signed-off-by: Sebastian Huber <sebastian.huber@embedded-brains.de>