From: Nick Andrew Date: Tue, 4 Mar 2008 23:05:40 +0000 (-0800) Subject: x86: Documentation/i386/IO-APIC.txt: fix description X-Git-Tag: v3.12-rc1~22255^2~7 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c0c20fb5a8f2e2eddf7f0e5467c7511fee907903;p=kernel%2Fkernel-generic.git x86: Documentation/i386/IO-APIC.txt: fix description The description of the interrupt routing doesn't match the (nice) diagram. Signed-off-by: Nick Andrew Signed-off-by: Andrew Morton Signed-off-by: Ingo Molnar Signed-off-by: Thomas Gleixner --- diff --git a/Documentation/i386/IO-APIC.txt b/Documentation/i386/IO-APIC.txt index f951666..30b4c71 100644 --- a/Documentation/i386/IO-APIC.txt +++ b/Documentation/i386/IO-APIC.txt @@ -70,7 +70,7 @@ Every PCI card emits a PCI IRQ, which can be INTA, INTB, INTC or INTD: These INTA-D PCI IRQs are always 'local to the card', their real meaning depends on which slot they are in. If you look at the daisy chaining diagram, -a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ2 of +a card in slot4, issuing INTA IRQ, it will end up as a signal on PIRQ4 of the PCI chipset. Most cards issue INTA, this creates optimal distribution between the PIRQ lines. (distributing IRQ sources properly is not a necessity, PCI IRQs can be shared at will, but it's a good for performance