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
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
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.