> This is not implicit -- CPU has to read INTACK reg. on OpenPIC. Which is what I meant... "implicit by reading the vector".
> Really implicit method is in action on x86 where CPU issues dual ACK bus > cycle to get > the vector form 8259... Which you can do on OpenPIC too. It's the same idea. The concept that obtaining the vector performs the ack. > > EOI is a more "high level" thing that some "intelligent" PICs that > > automatically raise the priority do to restore the priority to what it > > was before the interrupt occured. > > Thank you, I know. Even 8259 has the notion of priority and EOI works the > same way here. Ok, so why would you need an ack there then while eoi is just what you need ? :-) Also, that's interesting what you are saying about 8259... I should be able to convert ppc's i8259 to use fasteoi too... Ben. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
