Am Dienstag, 16. August 2005 19:20 schrieb Alan Cox:
>
> PCI interrupt line routing is used for all V-Bus devices. Thats all
> devices in any way on an internal bus of the north or south bridge. The
> quirk is harmless when applied to other devices.
>
> Note the description of the quirk is still wrong
>
>
> > > * For these devices, this register is defined to be 4 bits wide.
> > > * Normally this is fine. However for IO-APIC motherboards, or
> > > * non-x86 architectures (yes Via exists on PPC among other places),
> > > * we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
> > > * interrupts delivered properly.
>
> The interrupt line field is used to indicate the ISA type IRQ or the
> APIC pin used for the IRQ delivery. See the data sheet.
>
> The & 0x0F is the old hack used to get the ISA type IRQ line in use from
> the IRQ number.
>
Thanks, Bjorn and Alan!
After thinking again here is a 3rd version to change quirk_via_irq().
Motivation is to cleanup the IOAPIC-case:
Currently as of 2.6.13-rc6 new_irq is wrong then,
as dev->irq isn't the PIN number.
Solutions: either calculate correct new_irq (= PIN-Number & 0x0F)
or don't apply likely wrong value.
Following diff takes the 2nd way.
Well, VT8237 ignores the wrong new_irq in IOAPIC-Mode,
but its irritating to see dmesg print out nonsense then.
------
--- linux-2.6.13-rc6/drivers/pci/quirks.c 2005-08-08 11:46:05.000000000 +0200
+++ linux-2.6.13/drivers/pci/quirks.c 2005-08-18 11:55:50.000000000 +0200
@@ -497,9 +516,27 @@ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_V
* we must mask the PCI_INTERRUPT_LINE value versus 0xf to get
* interrupts delivered properly.
*/
+#ifdef CONFIG_X86_IO_APIC
+ extern struct hw_interrupt_type ioapic_edge_type;
+ extern struct hw_interrupt_type ioapic_level_type;
+#include <linux/irq.h>
+#endif
static void quirk_via_irq(struct pci_dev *dev)
{
u8 irq, new_irq;
+#ifdef CONFIG_X86_IO_APIC
+ {
+ irq_desc_t *desc = irq_desc + dev->irq;
+ if (desc &&
+ (desc->handler == &ioapic_edge_type ||
+ desc->handler == &ioapic_level_type)
+ )
+ return; /* We cannot guess the right
+ * new_irq with the simple hack below.
+ * lets just leave.
+ */
+ }
+#endif
new_irq = dev->irq & 0xf;
pci_read_config_byte(dev, PCI_INTERRUPT_LINE, &irq);
------
What do you think?
Karsten
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |