From: Benjamin Herrenschmidt <bh40@calva.net>
To: ostermann@cs.ohiou.edu
Cc: linuxppc-dev@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: PB3400 ethernet and Q1->Q3 upgrade
Date: Tue, 21 Sep 1999 16:15:56 +0200 [thread overview]
Message-ID: <19990921161556.026124@mailhost.mipsys.com> (raw)
On Tue, Sep 21, 1999, Shawn Ostermann <ostermann@cs.ohiou.edu> wrote:
>Unfortunately, I get in over my head very quickly when talking about
>hardware details. Do you have enough information to look into those
>points?
I think I found where this mysterious ethernet interrupt is. I don't have
one of those machines to test with, but you can find interesting things
in darwin's source code in the drvPExpert package (platform expert,
contains the motherboard specific stuffs).
Basically, it appears that Apple checks for the presence of ohare2
(pci106b,7). When available, the ethernet irq is "fixed" (xor'ed with
0x18) and a special ohare2 handler is cascaded on the fifth irq of ohare
(bit 27 or 28, there's apparently a bug in the comment).
The eth itself is on the fourth or fifth interrupt of ohare 2 controller.
(I'm afraid: did they put an entire second ohare just for an interrupt
controller ? Or do they also use the SCC for the modem ? Do you have 2
media bays on this machine ?)
So it may be possible to implement this the same way I implemented the
gatwick interrupts for the wallstreet.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-09-21 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-21 14:15 Benjamin Herrenschmidt [this message]
[not found] <19990921161556.026124>
1999-09-21 14:20 ` PB3400 ethernet and Q1->Q3 upgrade Benjamin Herrenschmidt
[not found] <19990922110700.018164@mailhost.mipsys.com>
1999-09-22 12:53 ` Shawn Ostermann
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=19990921161556.026124@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ostermann@cs.ohiou.edu \
/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).