From: Pete Popov <ppopov@embeddedalley.com>
To: Herbert Valerio Riedel <hvr@gnu.org>
Cc: sshtylyov@ru.mvista.com, linux-mips@linux-mips.org, jgarzik@pobox.com
Subject: Re: RFC: au1000_etc.c phylib rewrite
Date: Mon, 01 May 2006 12:15:45 -0700 [thread overview]
Message-ID: <1146510945.21947.44.camel@localhost.localdomain> (raw)
In-Reply-To: <1146510542.16643.10.camel@localhost.localdomain>
On Mon, 2006-05-01 at 21:09 +0200, Herbert Valerio Riedel wrote:
> hello *,
>
> I've started to rewrite the au1000_eth.c driver to make use of the new
> PHY framework in 2.6.x; see the attached patch for the current work in
> progress state;
>
> I'm a bit unsure what to do about those workarounds/hacks that are in
> the original au1000_eth.c driver (e.g. for the broadcom dual PHY);
Maybe you should dump that bcm dual phy support. I can't remember what
board it was on and whether that board is even supported still.
> any comments/ideas? shall I continue work on this au1xxx-eth
> phylib-rewrite, or is it of no use?
Seems like a good idea to me.
Pete
next prev parent reply other threads:[~2006-05-01 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-01 19:09 RFC: au1000_etc.c phylib rewrite Herbert Valerio Riedel
2006-05-01 19:15 ` Pete Popov [this message]
2006-05-01 20:05 ` Robin H. Johnson
2006-05-01 20:09 ` Mark Schank
2006-05-02 6:23 ` Herbert Valerio Riedel
2006-05-02 16:20 ` Mark Schank
2006-05-03 16:34 ` Herbert Valerio Riedel
2006-05-03 18:01 ` Mark Schank
2006-05-04 6:49 ` Robin H. Johnson
2006-05-04 9:17 ` RFC: new WIP version of au1000_eth.c phylib conversion (was Re: RFC: au1000_etc.c phylib rewrite) Herbert Valerio Riedel
2006-05-08 22:24 ` Andy Fleming
2006-05-09 2:04 ` Herbert Valerio Riedel
2006-05-05 0:36 ` RFC: au1000_etc.c phylib rewrite Andy Fleming
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=1146510945.21947.44.camel@localhost.localdomain \
--to=ppopov@embeddedalley.com \
--cc=hvr@gnu.org \
--cc=jgarzik@pobox.com \
--cc=linux-mips@linux-mips.org \
--cc=sshtylyov@ru.mvista.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