Re: [PATCH 2/2] Add libudev input-hotplug backend

2009-10-19 Thread Adam Jackson
On Fri, 2009-10-16 at 15:31 +1000, Peter Hutterer wrote: > On Fri, Oct 16, 2009 at 02:30:40PM +1000, Peter Hutterer wrote: > > On Wed, Oct 14, 2009 at 10:21:12PM +0200, Julien Cristau wrote: > > > If libudev is found, we use that for hotplug and disable the hal and > > > dbus backends. > > > We loo

Re: [PATCH 2/2] Add libudev input-hotplug backend

2009-10-15 Thread Peter Hutterer
On Fri, Oct 16, 2009 at 02:30:40PM +1000, Peter Hutterer wrote: > On Wed, Oct 14, 2009 at 10:21:12PM +0200, Julien Cristau wrote: > > If libudev is found, we use that for hotplug and disable the hal and > > dbus backends. > > We look for event devices with an "x11_driver" property. XKB > > configu

Re: [PATCH 2/2] Add libudev input-hotplug backend

2009-10-15 Thread Peter Hutterer
On Wed, Oct 14, 2009 at 10:21:12PM +0200, Julien Cristau wrote: > If libudev is found, we use that for hotplug and disable the hal and > dbus backends. > We look for event devices with an "x11_driver" property. XKB > configuration happens using xkb.{rules,model,layout,variant,options} > properties

[PATCH 2/2] Add libudev input-hotplug backend

2009-10-14 Thread Julien Cristau
If libudev is found, we use that for hotplug and disable the hal and dbus backends. We look for event devices with an "x11_driver" property. XKB configuration happens using xkb.{rules,model,layout,variant,options} properties. Arbitrary driver options can be set with a "x11_options." prefix. udev