Kok, Auke wrote:
That's why we want to introduce a second e1000 driver (named
differently, pick any name) that contains the new code base,
side-by-side into the kernel with the current e1000.
We do not want to introduce duplicate drivers for the same hardware. We
spend -years- before the old driver gets removed. There are installer
headaches with distros, with duplicate drivers. User confusion.
Problems abound, as past history shows.
I meant a new driver for ICH9 and later hardware, or whatever hardware
boundary between new-driver and old-driver you wish to pick.
That way the new driver doesn't carry all the old baggage with it, and
can go quietly into old age.
This would allow everyone to fallback and compare the new and old code
instantly, for several kernel releases at least. After that period, we
can retire the old codebase.
No it takes -years- to kill duplicate drivers, when you consider all the
transition effects. That is what history shows us time and again.
Given the size of the changes and the fact that this is an interal API
change that gigantically changes how e1000 internally works, there is
*no* way that we can introduce this change in any other way in my opinion.
The standard way to introduce big changes is to (a) do them, and then
(b) plot the steps involved in the transition, and create those steps
that lead us to the goal.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
