From: Andy Fleming <afleming@freescale.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Netdev <netdev@oss.sgi.com>,
Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: [RFC] Patch to Abstract Ethernet PHY support (using driver model)
Date: Fri, 14 Jan 2005 15:00:20 -0600 [thread overview]
Message-ID: <4D217F72-666F-11D9-8D70-000393C30512@freescale.com> (raw)
In-Reply-To: <20050114145518.GA21418@wohnheim.fh-wedel.de>
>> In fact, we use different switch chips connected to PPC4xx directly.
>> In this situation, in my NAPI IBM EMAC driver I just have special
>> "PHY-less" case which is trivial "fixed settings" one. And all this
>> PHY lib is completely unneeded bloat.
>
> Wrt. the proposed PHY lib, I agree. Didn't even bother to look at the
> code, it's mere size said enough.
Hmm... Before I spend too much time revising based on previous comments
ebs made, is there a general consensus that the code is much too large?
I know there's a lot in there, but the goal is to simplify PHY
management for all ethernet drivers, new and old, and thus reduce code
size, overall. Is this code heading in the right direction? Does it
do too much? Too little?
Andy Fleming
Open Source Team
Freescale Semiconductor, Inc
next prev parent reply other threads:[~2005-01-14 21:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 19:01 [RFC] Patch to Abstract Ethernet PHY support (using driver model) Andy Fleming
2004-12-23 21:00 ` Andy Fleming
2005-01-06 7:02 ` Eugene Surovegin
2005-01-06 17:13 ` Eugene Surovegin
2005-01-13 19:50 ` Andy Fleming
2005-01-13 21:21 ` Eugene Surovegin
2005-01-13 21:58 ` Jörn Engel
2005-01-14 1:00 ` Eugene Surovegin
2005-01-14 14:55 ` Jörn Engel
2005-01-14 15:25 ` Eugene Surovegin
2005-01-14 15:49 ` Jörn Engel
2005-01-14 21:00 ` Andy Fleming [this message]
2005-01-17 17:17 ` Jörn Engel
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=4D217F72-666F-11D9-8D70-000393C30512@freescale.com \
--to=afleming@freescale.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=netdev@oss.sgi.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).