From: geoff@collyer.net
To: mteege@gmail.com, 9fans@cse.psu.edu
Subject: Re: [9fans] Hardware for venti/fossil/cpu server
Date: Wed, 22 Sep 2004 02:24:41 -0700 [thread overview]
Message-ID: <3c38e0973b81ee280f074f4647d3d05a@collyer.net> (raw)
In-Reply-To: <88a4775604092201221495aa52@mail.gmail.com>
I've never heard of the built-in Gbe. You're probably better off
just buying an Intel PRO/1000 MT and putting it in.
SATA is supposed to just work, but I believe there's limited
experience with it so far on Plan 9.
The AMD64 shouldn't be a problem, as long you are content to run
it in 32-bit mode for now. 8[cal] don't yet generate the
instruction prefixes (prefaces?) for 64-bit addresses.
I'd also recommend avoiding built-in i8254[17]* controllers;
they aren't quite compatible with the igbe drivers in Plan 9
and need various bug workarounds in the drivers (no surprise,
the word `compatible' has been greatly watered-down by the
hardware vendors). I may get around to adding those
workarounds, but the reference Linux driver from Intel is
10,000 lines long, so it may not happen immediately.
I've always distrusted hardware built into the motherboard
and the current round of built-in Gbe controllers is doing
nothing to change that distrust. They're either broken
(the not-quite igbe), Broadcom or Brand X (Marvell).
I'm not sure how breaking the igbe controllers reduces
anybody's costs.
next prev parent reply other threads:[~2004-09-22 9:24 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 [this message]
2004-09-22 10:07 ` Nigel Roles
2004-09-22 10:18 ` geoff
2004-09-22 10:42 ` Nigel Roles
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=3c38e0973b81ee280f074f4647d3d05a@collyer.net \
--to=geoff@collyer.net \
--cc=9fans@cse.psu.edu \
--cc=mteege@gmail.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;
as well as URLs for NNTP newsgroup(s).