From: "Ronald G. Minnich" <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Intel 8254[17] and switches
Date: Sat, 16 Apr 2005 10:10:28 -0600 [thread overview]
Message-ID: <Pine.LNX.4.58.0504161007450.25437@enigma.lanl.gov> (raw)
In-Reply-To: <f56acd4ec156b8ecde37f1c82630fcca@coraid.com>
On Sat, 16 Apr 2005, Brantley Coile wrote:
> After a couple of weeks banging my head on the wall, I discover that the
> PXE firmware on the things can't even drive 1GbE. I couldn't find any
> mention of this fact in anything from Intel, unless one of the erata's
> on a sheet I got states this fact in an obscure way.
PXE firmware is shit. I would be willing to be they forward-ported their
eepro-100 firmware and made it just barely work on the new chips.
you know, it has happened before that a vendor will connect up the traces
backwards from chip to connector. The result is the kind of thing you are
seeing. It kind of works, but it doesn't work. Honestly, you'll see data
move, but you'll see a lot of problems too.
Any chance that is the case here? I think those chips should really be
fine. I can't imaging going to broadcom from those parts.
ron
prev parent reply other threads:[~2005-04-16 16:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 12:51 Brantley Coile
2005-04-16 16:10 ` Ronald G. Minnich [this message]
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=Pine.LNX.4.58.0504161007450.25437@enigma.lanl.gov \
--to=rminnich@lanl.gov \
--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).