![]() | |||||||||||
Messages in this thread |
From: Greg KH <greg@kroah.com> Date: Mon, 8 Oct 2007 21:39:09 -0700 > No, nothing cute in udev itself, but it seems that all distros that I > know of have a "load these modules now" type setting in their init > scripts that can be used here. > > I can't think of a way to enforce this load order on the modules > themselves due to the fact that OHCI might not even be needed for EHCI > devices on UHCI (Intel) based chipsets :( > > Can anyone else? The three modules perhaps should be a bundle of whatever ones you have enabled, and internally we can dispatch the initialization to occur in the correct order from a top-level module_init(). If the devices need to be initialized in a certain order in a situation like this, it really seems like it is the kernel's job to enforce it. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2007-10-09 06:49 [from the cache] ©2003-2008 | |||||||||||