linux-kernel - Trivial patch to Documentation/i386/IO-APIC.txt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 12 Feb 2008 12:08:43 +1100
From:	Nick Andrew <nick@...k-andrew.net>
To:	linux-kernel@...r.kernel.org
Subject: Trivial patch to Documentation/i386/IO-APIC.txt

The description of the interrupt routing doesn't match the (nice) diagram.

Signed-off-by: Nick Andrew <nick@...k-andrew.net>

Nick.

--- a/Documentation/i386/IO-APIC.txt	2007-10-10 06:31:38.000000000 +1000
+++ b/Documentation/i386/IO-APIC.txt	2008-02-12 11:57:08.000000000 +1100
@@ -68,7 +68,7 @@
 
 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/