linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Robert E Brose II <bob@kunk.qbjnet.com>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: IRQS on 6 Slot Macs
Date: Mon, 03 Nov 2003 17:54:41 +1100	[thread overview]
Message-ID: <1067842481.17970.8.camel@gaston> (raw)
In-Reply-To: <20031103033529.24416.qmail@kunk.qbjnet.com>


On Mon, 2003-11-03 at 14:35, Robert E Brose II wrote:

> A couple of things right off, the rage128 appears to be the only thing on
> irq 23 however 23 doesn't show up in /proc/interrupts meaning, I suppose,
> that it's not using the interrupt. So why does the drm complain?
>
> How come everything from slots 3-6 says it's on the same interrupt (25)?

I don't know what's up with the DRM not liking your interrupt. I can
answer for the sharing of USB, symbios and firewire interrupts: all 3
slots share one interrupt because of bad motherboard design :)
Basicallly, what they did when designing that machine was to use a
standard powersurge design with 3 slots and replace one of them
with a PCI<->PCI bridge. Since they didn't "know" how to get more
interrupt lines out of Grand Central, they just also stuffed all
interrupt lines together for those 4 slots (I'm pretty sure GC do
have spare lines they could have used, but that would have meant
updating Open Firmware to understand the layout, I doubt the people
who designed that machine wanted to dive into that).

Ben.


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

  reply	other threads:[~2003-11-03  6:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  3:35 IRQS on 6 Slot Macs Robert E Brose II
2003-11-03  6:54 ` Benjamin Herrenschmidt [this message]
2003-11-03 14:11   ` Bob Brose
2003-11-03 14:34     ` Geert Uytterhoeven
2003-11-03 21:40     ` Benjamin Herrenschmidt
2003-11-04  8:55   ` Jeff Walther
2003-11-04  9:14     ` Benjamin Herrenschmidt
     [not found]       ` <a04310102bbcda40d92fc@[199.170.89.159]>
     [not found]         ` <1067985081.707.124.camel@gaston>
2003-11-05  2:11           ` Jeff Walther
2003-11-05  2:46             ` Benjamin Herrenschmidt
2003-11-05  6:20               ` Jeff Walther
2003-11-05  7:18                 ` Benjamin Herrenschmidt
2003-11-05 17:39                   ` Jeff Walther
2003-11-06  7:07                     ` Brad Boyer
2003-11-06 13:18                       ` Michael R. Zucca
2003-11-06 16:44                       ` Jeff Walther
2003-11-05  9:47             ` Geert Uytterhoeven
2003-11-05 10:38               ` Michael Schmitz
2003-11-05 11:38                 ` Etsushi Kato
2003-11-03 11:30 ` Michel Dänzer
2003-11-03 14:40   ` Robert E. Brose II
2003-11-03 14:54     ` Michel Dänzer
  -- strict thread matches above, loose matches on Subject: below --
2003-11-03 21:30 Mich Lanners
2003-11-04  3:16 ` Benjamin Herrenschmidt
2003-11-04 20:27 Mich Lanners
2003-11-04 21:53 ` Jeff Walther
2003-11-04 21:29 Jeff Walther
2003-11-04 22:30 ` Geert Uytterhoeven
2003-11-05  1:48   ` Jeff Walther

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=1067842481.17970.8.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=bob@kunk.qbjnet.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).