netdev
[Top] [All Lists]

Re: [patch 0/4] 2.6.5-rc2-mm5 - r8169 queue

To: Francois Romieu <romieu@xxxxxxxxxxxxx>
Subject: Re: [patch 0/4] 2.6.5-rc2-mm5 - r8169 queue
From: Jeff Garzik <jgarzik@xxxxxxxxx>
Date: Tue, 30 Mar 2004 10:37:59 -0500
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20040329211441.B4744@electric-eye.fr.zoreil.com>
References: <20040329193604.A4744@electric-eye.fr.zoreil.com> <4068656D.2080103@pobox.com> <20040329211441.B4744@electric-eye.fr.zoreil.com>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
Francois Romieu wrote:
Jeff Garzik <jgarzik@xxxxxxxxx> :
[...]

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 in Thread] Current Thread [Next in Thread>
  • Re: [patch 0/4] 2.6.5-rc2-mm5 - r8169 queue, Jeff Garzik <=