On Wed, Oct 24, 2007 at 15:54:05 +0300, Daniel Stone wrote: > On Wed, Oct 24, 2007 at 02:47:06PM +0200, ext Julien Cristau wrote: > > On Tue, Oct 23, 2007 at 20:02:31 +0200, Michael Biebl wrote: > > > You were right, Julien. It was because of hal (specifically the file > > > /usr/share/hal/fdi/policy/10osvendor/10-x11-input.fdi) that the evdev > > > driver was enabled. > > > > BTW, should we change the fdi to load synaptics instead of evdev when it > > detects a touchpad? It seems most people are using that. > > Yep, seems sensible to me.
OK. Michael, the following patch seems to work for me:
--- 10-x11-input.fdi 2007-10-24 15:07:22.000000000 +0200
+++ 10-x11-input.fdi.new 2007-10-24 15:07:58.000000000 +0200
@@ -7,6 +7,9 @@
<match key="/org/freedesktop/Hal/devices/computer:system.kernel.name"
string="Linux">
<merge key="input.x11_driver" type="string">evdev</merge>
+ <match key="info.capabilities" contains="input.touchpad">
+ <merge key="input.x11_driver" type="string">synaptics</merge>
+ </match>
</match>
</match>
>
> > I'm using evdev right now on my laptop, but I need to run xinput to set
> > the device to relative mode every time I start X (and I had to modify
> > xinput to let me do that, because it doesn't think my touchpad is an
> > extended device).
>
> Ah, yes. I assume it was just checking for XExtensionDevice, instead of
> Device/Keyboard/Pointer?
>
Right.
Cheers,
Julien
signature.asc
Description: Digital signature
