From: "Timothy A. Seufert" <tas@mindspring.com>
To: Stefan Jeglinski <jeglin@4pi.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: arguing IRQ (was Re: dual IRQ 23)
Date: Tue, 5 Dec 2000 00:39:22 -0800 [thread overview]
Message-ID: <v04220801b652547c23e8@[10.0.0.42]> (raw)
In-Reply-To: <p04330100b650e03a5dcb@[192.168.0.1]>
At 1:09 AM -0500 12/4/00, Stefan Jeglinski wrote:
>So, is Geert right (PCI ok at least in this aspect, drivers are
>buggy)? Or are Ben/Michel right (drivers OK, PCI/IRQ buggy)?
PCI is in fact designed to share interrupts gracefully, as Geert
said. However, sharing doesn't look like the problem here: what
Michel and Ben are talking about is that the kernel fails to
correctly identify your card's true IRQ number. On these Macs there
is a fixed mapping between PCI slots and interrupt numbers,
determined by hardware. If software gets this mapping wrong, drivers
will hook into the wrong IRQ numbers and fail to work correctly.
According to Ben, this appears to be a problem in the kernel code
which discovers information about PCI devices (including interrupt
mappings) from an Open Firmware data structure, the OF device tree.
Apparently the interrupt assignment information in the device tree is
structured somewhat differently in Old World Macs such as yours when
devices are behind a PCI to PCI bridge. (Your combo card consists of
such a bridge plus two PCI devices.)
Tim Seufert
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-12-05 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-29 1:55 dual IRQ 23 (was: USB?; 2.2.18 no boot?; aic7xxx?) Stefan Jeglinski
2000-12-01 19:56 ` Michel Lanners
2000-12-03 20:41 ` Geert Uytterhoeven
2000-12-04 6:09 ` arguing IRQ (was Re: dual IRQ 23) Stefan Jeglinski
2000-12-05 8:39 ` Timothy A. Seufert [this message]
2000-12-04 14:35 ` dual IRQ 23 (was: USB?; 2.2.18 no boot?; aic7xxx?) Benjamin Herrenschmidt
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='v04220801b652547c23e8@[10.0.0.42]' \
--to=tas@mindspring.com \
--cc=jeglin@4pi.com \
--cc=linuxppc-dev@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).