Messages in this thread |  | | | Subject | Re: [RFC] Pushing device/driver binding decisions to userspace | | From | Arjan van de Ven <> | | Date | Mon, 13 Nov 2006 08:58:47 +0100 |
| |
> > So my ultimate goal is to somehow move this decision making to udev. My > plan is something along these lines:
well today you can already unbind from userspace. The decision to bind automatically is the right one for the kernel, since that is by far the most common one (99.9%+ of stuff has only one driver ever) and also if you have no drivers it's just hard for udev to run at all :)
udev can already unbind those few really rare cases it cares about, and then do the other driver and bind that...... Now; there is a second issue. If the choice for one or the other is consistent, we should consider fixing the kernel drivers to just not advertise the b0rked one.. (this assumes that both drivers are in the kernel and both are open source)
-- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org
- 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/
|  |