From: olson@anchor.engr.sgi.com (Dave Olson)
To: adevries@engsoc.carleton.ca (Alex deVries)
Cc: cpezzee@microsoft.com, linux@cthulhu.engr.sgi.com
Subject: Re: using ec3 on a Challenge S
Date: Wed, 28 Apr 1999 10:53:47 -0700 (PDT) [thread overview]
Message-ID: <199904281753.KAA79893@anchor.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.3.96.990428133838.9204B-100000@lager.engsoc.carleton.ca> from Alex deVries at "Apr 28, 99 01:42:22 pm"
Alex deVries wrote:
| You should probably try to figure out where on the GIO64 that is located,
| it shouldn't be too difficult with some guidance from folks at SGI. What
| ethernet controller is on there exactly?
It's basicly the same ethernet setup as the IP20 (r4k Indigo).
The driver is quite similar, but there are a few differences in
features. The DMA is the IP20 dma (hpc1, not hpc3), but the
ethernet chip is identical to the one on the indy/challenge S,
just some features enabled by hpc3 aren't present.
If you have an irix system, the HPC31 defines in hpc3.h provide
most of the necessary info. On irix, it's actually shipped as
a seperate binary driver from the onboard ethernet, because of
the dma/control register differences. It would be possible to
do it all in one driver, but we didn't bother. The source code
for irix is the same for both, with a few ifdefs.
Dave Olson, Silicon Graphics
http://reality.sgi.com/olson olson@sgi.com
WARNING: multiple messages have this Message-ID (diff)
From: olson@anchor.engr.sgi.com (Dave Olson)
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: cpezzee@microsoft.com, linux@cthulhu.engr.sgi.com
Subject: Re: using ec3 on a Challenge S
Date: Wed, 28 Apr 1999 10:53:47 -0700 (PDT) [thread overview]
Message-ID: <199904281753.KAA79893@anchor.engr.sgi.com> (raw)
Message-ID: <19990428175347.8e_fwkyiAtJIelPmwW4Cr5b70eh09lbycvL8KUQkCYo@z> (raw)
In-Reply-To: <Pine.LNX.3.96.990428133838.9204B-100000@lager.engsoc.carleton.ca> from Alex deVries at "Apr 28, 99 01:42:22 pm"
Alex deVries wrote:
| You should probably try to figure out where on the GIO64 that is located,
| it shouldn't be too difficult with some guidance from folks at SGI. What
| ethernet controller is on there exactly?
It's basicly the same ethernet setup as the IP20 (r4k Indigo).
The driver is quite similar, but there are a few differences in
features. The DMA is the IP20 dma (hpc1, not hpc3), but the
ethernet chip is identical to the one on the indy/challenge S,
just some features enabled by hpc3 aren't present.
If you have an irix system, the HPC31 defines in hpc3.h provide
most of the necessary info. On irix, it's actually shipped as
a seperate binary driver from the onboard ethernet, because of
the dma/control register differences. It would be possible to
do it all in one driver, but we didn't bother. The source code
for irix is the same for both, with a few ifdefs.
Dave Olson, Silicon Graphics
http://reality.sgi.com/olson olson@sgi.com
next prev parent reply other threads:[~1999-04-28 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 17:07 using ec3 on a Challenge S Chris Pezzee
1999-04-28 17:35 ` www.linux.sgi.com Matthias Kleinschmidt
1999-04-28 17:42 ` using ec3 on a Challenge S Alex deVries
1999-04-28 17:53 ` Dave Olson [this message]
1999-04-28 17:53 ` Dave Olson
1999-04-28 17:54 ` linus.linux.sgi.com status Ariel Faigon
1999-04-28 17:54 ` Ariel Faigon
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=199904281753.KAA79893@anchor.engr.sgi.com \
--to=olson@anchor.engr.sgi.com \
--cc=adevries@engsoc.carleton.ca \
--cc=cpezzee@microsoft.com \
--cc=linux@cthulhu.engr.sgi.com \
/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