On Tue, Nov 13, 2001 at 07:29:00PM +0100, Wolfgang Denk wrote: > In message <20011113072253.A4515@hq2> Victor Yodaiken wrote: > > > > Can you explain what you would like to happen? > > Try running normal ethernet on a SCC, handled by Linux, and assign > another frequent interrupt (for instance a CPM timer) to be handled > by a RT task and you will know what he means.
We don't support 860 in OpenRTL yet [although patches would be welcomed], but we do support 860 for customers and I don't see a problem with doing exactly what you propose. I still don't understand the technical issue if there is one. > > BTW: as I understand it, PPC Linux does have a "flat" model with the > > low level code reaching out to determine which device is responsible > > by looking at the second level interrupt controller. > > PPC Linux uses one function to register an interrupt on SIU level > (request_8xxirq()), and another to register interrupt on the CPM > (cpm_install_handler()). > > This is NOT a flat model. Linux does map all interrupts onto a flat model: you don't have to use cpm_install_handler I believe. [advertising omitted] -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] -- For more information on Real-Time Linux see: http://www.rtlinux.org/
