From: Tim Hockin <thockin@isunix.it.ilstu.edu>
To: torvalds@transmeta.com (Linus Torvalds)
Cc: siemer@panorama.hadiko.de (Robert Siemer),
jgarzik@mandrakesoft.com, linux-kernel@vger.kernel.org
Subject: Re: PCI IRQ routing problem in 2.4.0
Date: Sun, 28 Jan 2001 23:11:13 -0600 (CST) [thread overview]
Message-ID: <200101290511.XAA21997@isunix.it.ilstu.edu> (raw)
In-Reply-To: <Pine.LNX.4.10.10101282050180.5079-100000@penguin.transmeta.com> from "Linus Torvalds" at Jan 28, 2001 08:58:57 PM
> > 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]
>
> Your "link" values are in the range 1-4. Which makes perfect sense, but
> that's absolutely _not_ what the Linux SiS routing code expects (the code
> seems to expect them to be ASCII 'A' - 'D').
In reading the PIRQ specs, and making it work for our board, I thought
about this. PIRQ states that link is chipset-dependant. No chipset that I
have seen specifies what link should be. So, as this case demonstrates, it
may be 'A' - the value the chipset expects, or 1, the logical index.
Either one makes sense, assuming the PIRQ routing code knows what link
means. Here we see two BIOS vendors/versions that apparently do it
differently for the same chipset. Grrr.
-
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 5:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200101290323.TAA05252@penguin.transmeta.com>
2001-01-28 20:58 ` Robert Siemer
2001-01-29 4:29 ` Robert Siemer
2001-01-29 4:58 ` Linus Torvalds
2001-01-29 5:11 ` Tim Hockin [this message]
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=200101290511.XAA21997@isunix.it.ilstu.edu \
--to=thockin@isunix.it.ilstu.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®