Cc: Daniel Barkalow <barkalow@...>, Christoph Hellwig <hch@...>, Kok, Auke <auke-jan.h.kok@...>, Ingo Molnar <mingo@...>, Matthew Wilcox <matthew@...>, Linux Kernel Mailing List <linux-kernel@...>, NetDev <netdev@...>, e1000-list <e1000-devel@...>, linux-pci maillist <linux-pci@...>, Andrew Morton <akpm@...>, David S. Miller <davem@...>, Jesse Brandeburg <jesse.brandeburg@...>, Ronciak, John <john.ronciak@...>, Allan, Bruce W <bruce.w.allan@...>, Greg KH <greg@...>, Arjan van de Ven <arjan@...>, Rafael J. Wysocki <rjw@...>
No. I mean never ever remove the *configure* level thinking that "e1000 is
e1000".
There is no sense in *ever* showing it as two drivers to users, because
users do not see them as separate chipsets. They look identical, down to
the part names.
If it's a single family, and users can't even easily tell whether they
have version 1 or version 2 (PCI vs PCI-E), you shouldn't even ask them.
You should literally ask them: "do you want e1000 support".
That's it.
Once you have asked them that, you can then decide "ok, if you *really*
know what version of the chip you have, you can decide to only get limited
driver support".
But that's a secondary thing from a user perspective.
See the patch I already sent out.
Linus
--
