From: Matt Porter <mporter@kernel.crashing.org>
To: Pete Popov <ppopov@embeddedalley.com>
Cc: Ulrich Eckhardt <eckhardt@satorlaser.com>, linux-mips@linux-mips.org
Subject: Re: bitrot in drivers/net/au1000_eth.c
Date: Fri, 28 Jan 2005 10:20:56 -0700 [thread overview]
Message-ID: <20050128102056.A9216@cox.net> (raw)
In-Reply-To: <41FA6FF0.4060302@embeddedalley.com>; from ppopov@embeddedalley.com on Fri, Jan 28, 2005 at 09:01:36AM -0800
On Fri, Jan 28, 2005 at 09:01:36AM -0800, Pete Popov wrote:
> Ulrich Eckhardt wrote:
<snip>
> > 3. Split off the MII handling code or, better, reuse the facility already
> > provided by drivers/net/mii.c. This would mean a significant rewrite of
> > au1x00.c, including probably breaking things on the way.
>
> That's a possibility too but more code needs to be added to mii.c. I
> actually revisited the code yesterday and was trying to figure out
> how to clean it up. But someone told me that there is 2.6 work in
> progress to do this so I decided to just wait. Maybe someone knows
> more about it.
I suggest everyone take a look at the effort posted to netdev:
http://oss.sgi.com/archives/netdev/2004-12/msg00643.html
It's an attempt at a phy abstraction layer that goes the next
logical step after the minimal support provided in mii.h.
It's evolved out of the in-driver abstraction that is currently
used in the sungem, ibm_emac, and gianfar drivers in 2.6. It
was just a matter of time before somebody got tired of copying
the same PHY mgmt bits into every driver. :)
-Matt
next prev parent reply other threads:[~2005-01-28 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 14:01 bitrot in drivers/net/au1000_eth.c Ulrich Eckhardt
2005-01-28 17:01 ` Pete Popov
2005-01-28 17:20 ` Matt Porter [this message]
2005-01-28 18:15 ` Pete Popov
2005-01-29 10:04 ` Ulrich Eckhardt
2005-01-30 11:50 ` Ulrich Eckhardt
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=20050128102056.A9216@cox.net \
--to=mporter@kernel.crashing.org \
--cc=eckhardt@satorlaser.com \
--cc=linux-mips@linux-mips.org \
--cc=ppopov@embeddedalley.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