Hello, Greg KH wrote:
No, the main issue is the order _within_ the runlevel. Almost every driver is in the "main" device_initcall level. But the ordering within that level matters, and that is only definied by the Makefile order, no symbol resolution or anything else specific we can determine later.
Recent kernels produce modules.order which lists the makefile order of modules and is currently used by modprobe to determine which module to load when multiple modules match a device alias. It can take some work but I don't think it'll be too hard to make the fast loaded modules to observe link order. It would be nice to ship with a generic kernel and have some userland scripts which can link the dynamic image on the first boot (or when the list of loaded modules changes) and use it for subsequent boots while leaving the generic kernel as the 'safe' boot option. Thanks. -- tejun -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org