> To deal with the problem in the immediate term I'm going to actually > connect the legacy interrupts to the IO APIC as well so Linux doesn't > try to use the I8259 at all. >
Actually, I've got a question for this too. I'd like to hook up both the I8259 and the IO APIC at the same time, but the mechanism I have set up right now only allows one connection at a time. Basically, anything capable of receiving interrupts has a function to return a pin object which knows who it belongs to and which pin number it is. The return value is assigned to the output of the thing that triggers it to make the connection. That's worked really well, so what I'd like to do is just extend it to allow the param on the sender to be able to hold more than one connection and still be able to call something like "intPin->signalInterrupt()" in C++. Any suggestions on the best way to do that? Gabe _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
