[RFC PATCH] Initial libudev input-hotplug support

[Dan Nicholson]

On Tue, Oct 6, 2009 at 4:32 AM, Julien Cristau <jcristau at debian.org> wrote:
> On Thu, Oct  1, 2009 at 16:40:04 -0700, Dan Nicholson wrote:
>
>> On Thu, Oct 1, 2009 at 7:54 AM, Julien Cristau <jcristau at debian.org> wrote:
>> > I'm happy to remove the x11_options stuff from config/udev.c if there's
>> > a way to set options for hotplugged devices from the ddx.  Does driver
>> > selection also move to the ddx, leaving only xkb in config/?  Or should
>> > we have that in both, and let the ddx override the driver chosen by dix?
>>
>> I envisioned that the ddx would entirely be in control of the driver
>> since they're typically ddx specific anyway.
>
> As a distro, the nice thing about hal fdi or udev rules is that I can
> ship one to enable the evdev driver in the evdev driver package, same
> with synaptics, same with vmmouse, etc.  The other options AFAICS are to
> hardcode the driver choice in Xorg (but then we'll also need a fallback
> to evdev if synaptics isn't installed, and similar headaches), or have
> stuff configured in xorg.conf.  So at least for now I think I'll keep
> x11_driver in udev.

Definitely agree with that thinking. I'm just hoping that eventually
the file be /etc/X11/xorg.conf.d/synaptics.conf or such.

> If your patches go in I can't see any particular reason we'd want to
> change options in udev rules at a distro level, though (if the driver
> has bad default values, we should fix them there), so I'll remove this
> from v2 of my config/udev patch.  Does that sound ok?

I'd say leave the x11_options stuff in there for now since you already
have the code and there will be no other way to configure the devices.
If my patches land, we can always strip that part out. There's time
before 1.8 to get everything straightened out.

--
Dan