From: Jeff Garzik <jgarzik@pobox.com>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@oss.sgi.com
Subject: Re: [patch 0/4] 2.6.5-rc2-mm5 - r8169 queue
Date: Tue, 30 Mar 2004 10:37:59 -0500 [thread overview]
Message-ID: <40699457.1020304@pobox.com> (raw)
In-Reply-To: <20040329211441.B4744@electric-eye.fr.zoreil.com>
Francois Romieu wrote:
> Jeff Garzik <jgarzik@pobox.com> :
> [...]
>
>>I am pondering taking your latest version of r8169, and moving the
>>phy-related code from there to 8139cp.c. Then just add
>> MODULE_ALIAS("r8169");
>>and deleting r8169.c.
>>
>>The rationale is, 8169 is _exactly_ the same as 8139C+, except the phy
>>code and one or two bits in the chip registers. I would rather have
>>just one codebase, supporting one MAC (i.e. the RX/TX part) and multiple
>>phys.
>
>
> It seems appealing. Do you have a specific schedule in mind ?
schedules are an anathema to me ;-)
I was thinking about getting your initial patches into 2.6.x upstream so
that r8169 users at least have something usable while the phy code gets
moved over to 8139cp.c.
Jeff
prev parent reply other threads:[~2004-03-30 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-29 17:36 [patch 0/4] 2.6.5-rc2-mm5 - r8169 queue Francois Romieu
2004-03-29 12:40 ` Andi Kleen
2004-03-29 20:35 ` Francois Romieu
2004-04-02 23:00 ` [patch] 2.6.5-rc2 - r8169 DAC Francois Romieu
2004-04-03 2:08 ` Srihari Vijayaraghavan
2004-04-03 8:19 ` Francois Romieu
2004-03-29 17:37 ` [patch 1/4] 2.6.5-rc2-mm5 - r8169 queue Francois Romieu
2004-03-29 17:37 ` [patch 2/4] " Francois Romieu
2004-03-29 17:38 ` [patch 3/4] " Francois Romieu
2004-03-29 17:39 ` [patch 4/4] " Francois Romieu
[not found] ` <4068656D.2080103@pobox.com>
2004-03-29 19:14 ` [patch 0/4] " Francois Romieu
2004-03-30 15:37 ` Jeff Garzik [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=40699457.1020304@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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).