From: Brantley Coile <brantley@coraid.com>
To: 9fans@cse.psu.edu
Subject: [9fans] etherigbe.c
Date: Thu, 7 Apr 2005 20:58:07 -0400 [thread overview]
Message-ID: <830a180baf50d33ac3bf21dc23e6e710@coraid.com> (raw)
Well, I got the driver working for the 8254[17]GI parts. I did it by
cloning the driver as etherigbe0.c and removing everything that touched
the phy. Any references to mii were removed. It only matches the PCI
DIDs for these two chips and can be linked with the original.
We're racing to finish a product, so we don't have time, but we will
go back and fixup the old driver to know about the new internal phys.
We have the books on the parts so that won't be a problem.
One question I have, though, is why do I want to touch the phy anyway?
Does anyone have a firm reason, other than the general `that's the way
we've always done it.'
Jim?
Brantley
next reply other threads:[~2005-04-08 0:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-08 0:58 Brantley Coile [this message]
2005-04-08 2:13 ` [9fans] plan9.log arisawa
2005-04-08 3:12 ` [9fans] etherigbe.c jmk
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=830a180baf50d33ac3bf21dc23e6e710@coraid.com \
--to=brantley@coraid.com \
--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).