From: Bob Brose <bob@kunk.qbjnet.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Robert E Brose II <bob@kunk.qbjnet.com>,
linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: IRQS on 6 Slot Macs
Date: Mon, 3 Nov 2003 08:11:25 -0600 (CST) [thread overview]
Message-ID: <20031103141125.10229.qmail@kunk.qbjnet.com> (raw)
In-Reply-To: <1067842481.17970.8.camel@gaston>
User Benjamin Herrenschmidt says:
> 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.
I suppose then that I should reorder the cards so that the ones generating
the most interrupts would be in the first 2 slots? It's pretty funny
having the possibility of the use of lots of irqs then ending up with
x86 style sharing. :(
Bob
--
/~\ The ASCII | Robert E. Brose II N0QBJ
\ / Ribbon Campaign | http://www.qbjnet.com/
X Help cure | mailto:bob@qbjnet.com
/ \ HTML Email | public key at http://www.qbjnet.com/key.html
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-03 14:11 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
2003-11-03 14:11 ` Bob Brose [this message]
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=20031103141125.10229.qmail@kunk.qbjnet.com \
--to=bob@kunk.qbjnet.com \
--cc=benh@kernel.crashing.org \
--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 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.