Cc: Jeff Garzik <jeff@...>, 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@...>, Linus Torvalds <torvalds@...>, 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@...>
you try to argue against a strong and established concept that Linux
always had from day one on: DRIVER_X=y means the user prefers that
driver so strongly that he has selected it built-in. Such drivers are
special in every sense: they run first before any of the module init,
they cannot be disabled, etc. etc.
The only case where that should be overriden as the primary driver for
that piece of hardware if _another_ driver is built-in _too_.
... which is exactly the E1000=y && E1000E=m regression that bit me and
the simple solution of forcing E1000E to follow the mode of the E1000
driver solves it.
The most common distro setup is E1000=m and E1000E=m. The most common
embedded setup is _one_ of the two drivers as =y. So i'm not sure why
you are arguing about all this. Please just fix this bug, simple as
that.
Ingo
--
