Touchpad "tapping" changes in 2.6.11?
Hi there.
I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in alps.c and now it's working like a charm again.
Maybe the hardware tapping-thing should be configurable via some boot or config option?
Signature · 1 line
Henrik Persson
Quoted 8 lines · Henrik Persson
Hi there.
I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in
alps.cand now it's working like a charm again.
Hi,
Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping.
Quoted 3 lines
Maybe the hardware tapping-thing should be configurable via some boot or config option?
After all quirks are worked out I think tapping will be controlled via mousedev.tap_time parameter when using legacy interfaces (dev/input/mouseX) and Peter's X driver when using native event interface.
Signature · 1 line
Dmitry
Quoted 12 lines · Dmitry Torokhov
Quoted 8 lines · Henrik Persson
Hi there.
I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in
alps.cand now it's working like a charm again.
Quoted 4 lines
Hi,
Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping.
Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm booting with psmouse.proto=exps now, and it's working the way I'm used to now.
The Aspire 1300-series is quite different from the 1350 ones.. The touchpad on the 1300 will work like a charm without the synaptics driver (but no fancy stuff is supported, I guess). Before you could boot and be happy without the synaptics driver, now you probably have to install the synaptics driver to be happy.. Maybe that's not so good. :)
Could this touchpad use the "exps" proto as default and then you could reconfigure if you want to use the ALPS driver..?
Signature · 1 line
Henrik Persson
Quoted 22 lines · Henrik Persson
Quoted 12 lines · Dmitry Torokhov
Quoted 8 lines · Henrik Persson
Hi there.
I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in
alps.cand now it's working like a charm again.Quoted 4 lines
Hi,
Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping.
Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm booting with psmouse.proto=exps now, and it's working the way I'm used to now.
Quoted 9 lines
The Aspire 1300-series is quite different from the 1350 ones.. The touchpad on the 1300 will work like a charm without the synaptics driver (but no fancy stuff is supported, I guess). Before you could boot and be happy without the synaptics driver, now you probably have to install the synaptics driver to be happy.. Maybe that's not so good. :)
Could this touchpad use the "exps" proto as default and then you could reconfigure if you want to use the ALPS driver..?
We (well Peter and Vojtech mostly as I don't have ALPS touchpad in my box) are trying to make ALPS work as it was working before even without Synaptics X driver without any additional options, please bear with us.
Still I think having Synaptics driver installed is the best way in the end simply because it has a lot of knobs so one can adjust tpouchpad's behavior to his/her liking. Maybe once distibutions start packaging and activating it by default it will be less of an issue.
Signature · 1 line
Dmitry
Quoted 23 lines · Dmitry Torokhov
Quoted 22 lines · Henrik Persson
Quoted 10 lines · Dmitry Torokhov
Quoted 5 lines · Henrik Persson
I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in
alps.cand now it's working like a charm again.Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping.
Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm booting with psmouse.proto=exps now, and it's working the way I'm used to now.
The Aspire 1300-series is quite different from the 1350 ones.. The touchpad on the 1300 will work like a charm without the synaptics driver (but no fancy stuff is supported, I guess). Before you could boot and be happy without the synaptics driver, now you probably have to install the synaptics driver to be happy.. Maybe that's not so good. :)
Quoted 7 lines
Quoted 2 lines
Could this touchpad use the "exps" proto as default and then you could reconfigure if you want to use the ALPS driver..?
We (well Peter and Vojtech mostly as I don't have ALPS touchpad in my box) are trying to make ALPS work as it was working before even without Synaptics X driver without any additional options, please bear with us.
I have some touchpad related patches in my tree, which I have uploaded here:
http://web.telia.com/~u89404340/patches/touchpad/2.6.11/
All of these patches are already in -mm I think.
Quoted 4 lines
Still I think having Synaptics driver installed is the best way in the end simply because it has a lot of knobs so one can adjust tpouchpad's behavior to his/her liking. Maybe once distibutions start packaging and activating it by default it will be less of an issue.
Fedora Core 3 already does that if I remember correctly.
Signature · 2 lines
Peter Osterlund - [email protected] http://web.telia.com/~u89404340
Quoted 8 lines · Peter Osterlund
Quoted 4 lines · Dmitry Torokhov
Still I think having Synaptics driver installed is the best way in the end simply because it has a lot of knobs so one can adjust tpouchpad's behavior to his/her liking. Maybe once distibutions start packaging and activating it by default it will be less of an issue.
Fedora Core 3 already does that if I remember correctly.
It does have synaptics driver packaged but if I remember correctly it is not automatically selected during installation.
Signature · 1 line
Dmitry