https://bugzilla.novell.com/show_bug.cgi?id=173647#c19 --- Comment #19 from Kay Sievers <kasievers@novell.com> 2007-08-10 12:15:21 MST --- (In reply to comment #17 from Jiri Benc)

Do you know (In reply to comment #16 from Kay Sievers)

...

There is infrastructure in the kernel and udev now, to allow per-device driver binding configuration with udev rules, but this is not enabled by default. It will need a lot of testing, as it completely changes how Linux handles driver binding. We may get ready for that in the next months.

It is possible (and the functionality is there for a really long time) to use bind/unbind sysfs attributes to change the driver on the fly - even when you have both modules loaded. Why you does not use this? It's thoroughly tested and works without problems.

Thanks for letting me know what we can do in the driver core. :) It just doesn't make sense to let a random kernel driver attach to the device, and then read the configuration and find out to unbind and bind the device to another driver. It creates all sorts of races, where the device is already in used by other subsystems. Like you can just unbind a device with an already automounted filesystem and such things. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.