From: Nigel Roles <nigel@9fs.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Hardware for venti/fossil/cpu server
Date: Wed, 22 Sep 2004 11:42:44 +0100 [thread overview]
Message-ID: <41515724.9090600@9fs.org> (raw)
In-Reply-To: <24f622bf465e6bbf6326088add97540c@collyer.net>
geoff@collyer.net wrote:
>Thanks for the explanation, Nigel.
>
>I can see now why the motherboard makers want to include a CSA
>version of the igbe, I just don't see why they felt the
>need to break the CSA version of the igbe in the process.
>I guess it's part of this crazy business of making the
>ether drivers micromanage the configuration of the PHYs
>and EEPROMs and other irrelevant rubbish that the hardware
>ought to be taking care of internally (or at least setting
>to sensible default state initially).
>
>
>
Actually on closer inspection the marvell chip is external on the Asus
motherboard, and still only connected via (!) PCI.
Only the Marvell PHY is used by Nvidia, and the embedded Gbe is their
own.
The linux driver for the Marvell chip (Yukon aka SysKonnect sk98)
is 35000 lines. Sorry, that's not fair: 43000 including headers. See,
I said 2000 lines for the Nvidia driver was nothing.
Thus the Asus board is an example of how not to connect your
Gbe.
I'm not about to try it, but I suspect getting Plan 9 to work on the
nForce 3 chipsets would not be too bad.
next prev parent reply other threads:[~2004-09-22 10:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 8:22 Matthias Teege
2004-09-22 9:24 ` geoff
2004-09-22 10:07 ` Nigel Roles
2004-09-22 10:18 ` geoff
2004-09-22 10:42 ` Nigel Roles [this message]
2004-09-22 15:01 ` jmk
2004-09-23 4:25 ` vdharani
2004-09-22 23:18 ` geoff
2004-09-22 15:19 jmk
2004-09-22 16:21 ` Matthias Teege
2004-09-22 22:57 ` geoff
2004-09-24 0:40 ` Kenji Okamoto
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=41515724.9090600@9fs.org \
--to=nigel@9fs.org \
--cc=9fans@cse.psu.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).