Dale Farnsworth wrote: > Create and register a board-specific interrupt driver. Assign it > a range of irqs (non-conflicting with the main interrupt driver). > When called with an irq outside its range, the board-specific driver > routines forward the call to the main driver. The board-specific driver > does a request_irq at init time for the one main irq it is multiplexing.
Yes! Flatten the cascaded interrupts to IRQs outside the CPU's, range, and write a software multiplexer that registers for the one IRQ the CPU knows. Right? That's much better than what I had in mind. Thanks, -kb ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
