From: Jeff Walther <trag@io.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: IRQS on 6 Slot Macs
Date: Tue, 4 Nov 2003 15:53:59 -0600 [thread overview]
Message-ID: <a04310106bbcdcc771453@[199.170.89.159]> (raw)
In-Reply-To: <E1AH7lb-0000FE-00@piglet.grunz.lu>
At 21:27 +0100 11/04/2003, Mich Lanners wrote:
>> However, I can't help but wonder if all that lovely video circuitry
>> on the 7500 and 8500 requires any interrupts and if so, where they
>> come from. Do they recycle the interrupts for slots 4 -6 or are
>> there other interrupts available on GC besides the ones for the six
>> slots?
>
>Here is my all-slots-filled config on a 7600:
>
>00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 03)
> Flags: bus master, medium devsel, latency 32, IRQ 22
>00:0d.0 Unknown mass storage controller: Promise Technology, Inc.
>20262 (rev 01)
> Flags: bus master, medium devsel, latency 32, IRQ 23
>00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
> Flags: bus master, medium devsel, latency 32, IRQ 24
>00:0f.0 VGA compatible controller: Matrox Graphics, Inc. MGA 2064W
>[Millennium] (rev 01) (prog-if 00 [VGA])
> Flags: stepping, medium devsel, IRQ 25
>00:10.0 Class ff00: Apple Computer Inc. Grand Central I/O (rev 02)
> Flags: bus master, medium devsel, latency 32, IRQ 22
>01:0b.0 Non-VGA unclassified device: Apple Computer Inc. Control Video
> Flags: fast devsel, IRQ 26
>01:0d.0 Class ff00: Apple Computer Inc. PlanB Video-In (rev 01)
> Flags: bus master, medium devsel, latency 32, IRQ 28
>
>So yes, video-in and graphics have separate interrupts. But those could
>be the same IRQ's as used on slots 4-6 on 9x00 machines. AFAIK, there
>have been no machines with video circuitry _and_ 6 PCI slots.
Thank you, michel. That will get me quite a ways along on that inquiry.
>I have no info about video-in; but I think I remember some site
>somewhere with all possible device trees online. You might find more
>info there...
I have that site bookmarked somewhere--at least I think it's the same
site. I just haven't checked it in a while. However, I think that
the device tree only generates a listing if there is a PCI card
installed in the slot, and as I recall, most of the machines listed
only had one or two PCI cards installed. Still, it's worth a look to
me.
I have a hardware project in mind, but am not actively working on it.
So, when discussion that touches on it comes up, I'll pop up for a
bit to gather/share what info I can, but until I move this to the
front of my hobby queue I won't make a lot of progress.
The thing I'm interested in is building a PowerSurge with three or
four Bandits. The architecture supports it, according to Apple
docs, but the big question is whether the actual implementation of
chips supports the full architecture or just a subset. For example,
one would need twelve interrupts for PCI slots (at least) with four
Bandits. Are there six more external interrupts available on GC?
And how could we ever figure that one out, unless someone sneaks into
a vault at Apple? (Or one could build that hypothetical machine with
6 PCI slots and built-in video which you mentioned above.)
Another essential question is whether there are sufficient
arbitration lines on Hammerhead to support three or four Bandits.
And the thing that usually kills my ambition to make this my primary
hobby at the moment is the firmware mods it would take. I'm into
hardware and not much of a programmer.
As to how I would build such a machine, if Apple's chips supported
it, the S900 has a second CPU slot on the motherboard. However,
that slot could be used for a CPU Bus expansion card, because almost
all the required signals are available there. So, one could put
two or three Bandits on a daughter card, install the card in the
secondary CPU slot on the S900 and run cables from the daughter card
to the PCI backplanes for the additional Bandits. Actually, it
would be fairly trivial to build a daughter card with a single Bandit
on it for the S900, adding three PCI slots....One need only copy
connections from the 9500 in order to do that.
Jeff Walther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-11-04 21:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 20:27 IRQS on 6 Slot Macs Mich Lanners
2003-11-04 21:53 ` Jeff Walther [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-04 21:29 Jeff Walther
2003-11-04 22:30 ` Geert Uytterhoeven
2003-11-05 1:48 ` Jeff Walther
2003-11-03 21:30 Mich Lanners
2003-11-04 3:16 ` Benjamin Herrenschmidt
2003-11-03 3:35 Robert E Brose II
2003-11-03 6:54 ` Benjamin Herrenschmidt
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
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='a04310106bbcdcc771453@[199.170.89.159]' \
--to=trag@io.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