linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: jeglin@4pi.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: dual IRQ 23 (was: USB?; 2.2.18 no boot?; aic7xxx?)
Date: Fri, 1 Dec 2000 20:56:28 +0100 (CET)	[thread overview]
Message-ID: <200012011956.UAA00670@piglet.grunz.lu> (raw)
In-Reply-To: <p04330100b64a0cac23a1@[192.168.0.1]>


Hi all,

On  28 Nov, this message from Stefan Jeglinski echoed through cyberspace:
> lspci -vv is attached at the end. The key point is that the entry for
> the Adaptec 2940UW card and the Orangelink USB card BOTH say:
>
> 	Interrupt: pin A routed to IRQ 23

> 00:0d.0 SCSI storage controller: Adaptec AIC-7881U
[snip]
> 	Interrupt: pin A routed to IRQ 23

> 00:0e.0 Ethernet controller: Digital Equipment Corporation DECchip
> 21142/43 (rev 41)
[snip]
> 	Interrupt: pin A routed to IRQ 24
>
> 00:0f.0 PCI bridge: Action Tec Electronics Inc: Unknown device 0100
> (rev 11) (prog-if 00 [Normal decode])
>
[snip]
> 01:0c.0 FireWire (IEEE 1394): NEC Corporation: Unknown device 00cd
> (rev 01) (prog-if 10 [OHCI])
[snip]
> 	Interrupt: pin A routed to IRQ 1
       This is most certainly wrong -> ^
>
> 01:0d.0 USB Controller: OPTi Inc. 82C861 (rev 10) (prog-if 10 [OHCI])
[snip]
> 	Interrupt: pin A routed to IRQ 23
                        and this too ->^^

Bot of these devices should get IRQ25. Why? Because on Macs, all four
IRQ lines of a PCI slot are OR'ed together on the bridge chip.
Therefore, there is one single fixed IRQ per PCI slot. So, the devices
behind the PCI-to-PCI bridge in slot 00:0f should all have the same IRQ,
which should be, following the obvious logic, IRQ 25.

Either a problem with the P2P bridge code in Linux, or with detecting
the IRQ's out of OF, as Ben suggested.

Stefan, you could try hardcoding that IRQ in the PCI fixup code, or in
the driver, and see whether that works...

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-12-01 19:56 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 [this message]
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
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=200012011956.UAA00670@piglet.grunz.lu \
    --to=mlan@cpu.lu \
    --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).