diff options
| author | Nick Andrew <nick@nick-andrew.net> | 2008-03-04 15:05:40 -0800 |
|---|---|---|
| committer | Ingo Molnar <mingo@elte.hu> | 2008-03-26 22:23:40 +0100 |
| commit | c0c20fb5a8f2e2eddf7f0e5467c7511fee907903 (patch) | |
| tree | 311ef4b323d09743d1d949e25039dc67871f7bcf /Documentation | |
| parent | 5254149f6c4e938fea3735183434e208097bd188 (diff) | |
| download | linux-c0c20fb5a8f2e2eddf7f0e5467c7511fee907903.tar.bz2 | |
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 <nick@nick-andrew.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'Documentation')
| -rw-r--r-- | Documentation/i386/IO-APIC.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/i386/IO-APIC.txt b/Documentation/i386/IO-APIC.txt index f95166645d29..30b4c714fbe1 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 |