From: Robert Siemer <Robert.Siemer@gmx.de>
To: torvalds@transmeta.com, jgarzik@mandrakesoft.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: PCI IRQ routing problem in 2.4.0
Date: Mon, 29 Jan 2001 05:29:50 +0100 [thread overview]
Message-ID: <20010129052950H.siemer@panorama.hadiko.de> (raw)
In-Reply-To: <200101290323.TAA05252@penguin.transmeta.com>
In-Reply-To: <20010128215812H.siemer@panorama.hadiko.de> <200101290323.TAA05252@penguin.transmeta.com>
From: Linus Torvalds <torvalds@transmeta.com>
> Another one..
> Robert, can you get the dump_pirq script from the pcmcia_cs package
> and send the output to us?
...it seems to reflect my settings in the bios:
Interrupt routing table found at address 0xf0a50:
Version 1.0, size 0x0080
Interrupt router is device 00:01.0
PCI exclusive interrupt mask: 0x0000 []
Compatible router: vendor 0x1039 device 0x0008
Device 00:0c.0 (slot 1): SCSI storage controller
INTA: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Device 00:0b.0 (slot 2): VGA compatible controller
INTA: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Device 00:0a.0 (slot 3): Ethernet controller
INTA: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Device 00:09.0 (slot 4): Multimedia video controller
INTA: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Device 00:01.0 (slot 0): ISA bridge
INTA: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Device 00:13.0 (slot 0): VGA compatible controller
INTA: link 0x01, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTB: link 0x02, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTC: link 0x03, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
INTD: link 0x04, irq mask 0x1eb8 [3,4,5,7,9,10,11,12]
Interrupt router at 00:01.0: SiS 85C503 PCI-to-ISA bridge
INTA (link 0x41): irq 12
INTB (link 0x42): irq 14
INTC (link 0x43): irq 10
INTD (link 0x44): irq 11
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 4:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-28 20:58 PCI IRQ routing problem in 2.4.0 Robert Siemer
[not found] ` <200101290323.TAA05252@penguin.transmeta.com>
2001-01-29 4:29 ` Robert Siemer [this message]
2001-01-29 4:58 ` Linus Torvalds
2001-01-29 5:11 ` Tim Hockin
2001-01-29 6:03 ` Linus Torvalds
2001-01-30 0:50 ` Via PCI IRQ routing problem related? (was: PCI IRQ routing problem in 2.4.0) Pete Toscano
2001-01-29 5:29 ` PCI IRQ routing problem in 2.4.0 (SiS results) Aaron Tiensivu
2001-01-29 5:50 ` Linus Torvalds
2001-01-29 7:10 ` PCI IRQ routing problem in 2.4.0 (SiS results part 2) Aaron Tiensivu
2001-01-29 7:21 ` Linus Torvalds
2001-01-29 7:11 ` Aaron Tiensivu
2001-01-29 5:30 ` PCI IRQ routing problem in 2.4.0 (SiS results) Aaron Tiensivu
2001-01-29 6:08 ` PCI IRQ routing problem in 2.4.0 Robert Siemer
2001-01-29 6:24 ` Linus Torvalds
2001-01-29 7:11 ` Robert Siemer
2001-01-29 7:41 ` Linus Torvalds
2001-01-29 17:19 ` Robert Siemer
[not found] <Pine.LNX.4.21.0101291230070.29065-100000@notebook.diehl.home>
2001-01-29 14:41 ` Jeff Garzik
[not found] <Pine.LNX.4.21.0101291801580.29065-400000@notebook.diehl.home>
2001-01-29 17:34 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010129052950H.siemer@panorama.hadiko.de \
--to=robert.siemer@gmx.de \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=siemer@panorama.hadiko.de \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.