Jon Masters wrote: >>> That is precisely what I'm saying, and more. >> Oops, then modprobe needs to be updated too. Jon, can you please put >> this onto your to-do list too? > > But the thing Rusty is also getting at (so I think) is that this might > not be the way to fix the "problem". Perhaps using the rebinding bits in > the kernel might be the best way to solve this in the longer term. I can > fix both depmod and modprobe, but I would appreciate some more input :) Proper solution : module loader with sane default order (which again should be specified by developers) and allows the user to choose which module to use. Complete but probably overkill solution : Don't let drivers probe devices on load. Control device binding per-device such that different devices of the same type can attach to different drivers. This is somewhat necessary between ahci and ata_piix because one is not subset of the other but controlling loading order seems to do the trick till now. > Alternatives are a config option to only load the first match for now, > and to load based on the Modules.order. Thoughts? That doesn't really change anything other than saving memory for the second module. Also, it's incomplete solution because the first module might or might not attach to the device. Sometimes device ID isn't enough to determine whether a specific driver can be used or not. Thanks. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
