Hi, why not simply placing a new request_cascaded_irq() with an additional controller/device identifier beside request_irq().
If you map the functionality to the original functions the rest of the code could stay unchanged. You can even map the old function calls using macros. (If you like to you can use device 0 for a virtual mapping too. But I wouldn't. :) request_irq() could be left unchanged and new patches could use a single registration function. So everyone should stay happy. Stephan ** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
