How does one enfrce eth device ordering at run time, when drivers are compiled in?
Jeff Garzik wrote: > Martin Michlmayr wrote: > >> From: Ilya A. Volynets-Evenbakh <[EMAIL PROTECTED]> >> >> Move meth.o upwards in Makefile since it's built-in and should be eth0 >> >> Since meth is the built-in Ethernet card on SGI O2 it makes sense for >> it to be eth0, even if there is also another network card in PCI slot. >> Therefore move the meth.o entry in the Makefile further up. This >> change has no negative side-effect and is therefore useful even in >> the days of udev. >> >> Signed-off-by: Ilya A. Volynets-Evenbakh <[EMAIL PROTECTED]> >> Signed-off-by: Martin Michlmayr <[EMAIL PROTECTED]> > > > NAK. Imagine if we did this for all platforms... you would never > stop churning the Makefile, because there is no perfect order. Its > policy. Its just to the distribution, not the kernel, to enforce > preferences like this. Don't depend on kernel Makefile driver ordering. > > Jeff > > > -- Ilya A. Volynets-Evenbakh Total Knowledge. CTO http://www.total-knowledge.com - 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
