Kok, Auke wrote:
I don't think that anyone besides you and maybe one or two others are interested in doing this rewrite from scratch.
I count myself as one of those others. :) I don't think it's a rewrite though; it's a rework.
The rest of us would rather see something much more similar to my original suggestion which relieves the ich9-wishes for everyone and provides a good starting point to go forward. Not to mention that a lot of that code is already there, and at least cleaned up quite a bit already.
But the structure of it isn't right, as mentioned by Jeff and I in previous posts. Any restructuring of your new driver will obviously take time. In my view using the urgency of needing ich9 support to get the new driver in isn't the right tradeoff. Perhaps the ich9 code should be backported into the existing e1000, which is where this thread started? This will buy time to restructure the new driver to make sure it is right for the future.
I agree with Jeff that the initial version of the new driver should have only essential features - bells and whistles can be added incrementally.
-- James Chapman Katalix Systems Ltd http://www.katalix.com Catalysts for your Embedded Linux software development - 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
