Re: New PCI IRQ routing code for pre9-2

• Previous message: Ishikawa: "Re: Problem: shell prompt doesn't return although the invoked program calls _exit()."
• In reply to: Jeff Garzik: "Re: New PCI IRQ routing code for pre9-2"
• Next in thread: Linus Torvalds: "Re: New PCI IRQ routing code for pre9-2"
• Reply: Linus Torvalds: "Re: New PCI IRQ routing code for pre9-2"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Jeff!

> No change after patches -- the Via 686A IRQ assignment code still has my
> CardBus devices on interrupt pin A, while telling the motherboard to
> assign IRQs to interrupt pin B.

   The PIRQ pins on Via 686A aren't the same as PCI interrupt pins of the
particular device. The mapping device pins -> PIRQ pins is contained in
the PIRQ table provided by the BIOS, but the meaning of the `pirq' values
in this table is chipset specific. I'm now trying to get some detailed
info from VIA.

                                Have a nice fortnight

-- 
Martin `MJ' Mares <mj@ucw.cz> <mj@suse.cz> http://atrey.karlin.mff.cuni.cz/~mj/
"RAM = Rarely Adequate Memory"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

• Next message: regardinginfo12@earthlink.net: "We can list Your Website"
• Previous message: Ishikawa: "Re: Problem: shell prompt doesn't return although the invoked program calls _exit()."
• In reply to: Jeff Garzik: "Re: New PCI IRQ routing code for pre9-2"
• Next in thread: Linus Torvalds: "Re: New PCI IRQ routing code for pre9-2"
• Reply: Linus Torvalds: "Re: New PCI IRQ routing code for pre9-2"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat May 20 2000 - 11:10:01 EDT