Alps: No edge-scrolling since 2.6.34-rc5
It looks like the "Acer Aspire One 532h" and the "HP Pavilion dm3" have the same signature but they behave differently.
As a result commit 5e28d8eb68 "Input: ALPS - add signature for HP Pavilion dm3 laptops" fixes things for dm3 but breaks the Acer Aspire One 532h which was working (with a userspace driver maybe??).
Here is the relevant "i8042.debug" output from bz 15893:
drivers/input/serio/i8042.c: d4 -> i8042 (command) [535] drivers/input/serio/i8042.c: e9 -> i8042 (parameter) [535] drivers/input/serio/i8042.c: fa <- i8042 (interrupt, 1, 12) [535] drivers/input/serio/i8042.c: 73 <- i8042 (interrupt, 1, 12) [536] drivers/input/serio/i8042.c: 02 <- i8042 (interrupt, 1, 12) [536] drivers/input/serio/i8042.c: 64 <- i8042 (interrupt, 1, 12) [536]
What's the right way to handle this?
regards,
dan carpenter
Hi Dan,
Quoted 6 lines · Dan Carpenter
It looks like the "Acer Aspire One 532h" and the "HP Pavilion dm3" have the same signature but they behave differently.
As a result commit
5e28d8eb68"Input: ALPS - add signature for HP Pavilion dm3 laptops" fixes things for dm3 but breaks the Acer Aspire One 532h which was working (with a userspace driver maybe??).
There were issues with this change, so it was reverted in the input tree. Specifically, it seems that these devices operate under a different protocol that the Linux driver does not understand yet.
As for when it should propagate to Linus' tree, Dmitry should have a better idea.
I'm sorry the change has caused you issues.
-- Chase
Quoted 6 lines · Chase Douglas
Hi Dan,
Quoted 3 lines · Dan Carpenter
It looks like the "Acer Aspire One 532h" and the "HP Pavilion dm3" have the same signature but they behave differently.
Quoted 8 lines
Quoted 3 lines
As a result commit
5e28d8eb68"Input: ALPS - add signature for HP Pavilion dm3 laptops" fixes things for dm3 but breaks the Acer Aspire One 532h which was working (with a userspace driver maybe??).There were issues with this change, so it was reverted in the input tree. Specifically, it seems that these devices operate under a different protocol that the Linux driver does not understand yet.
OK. Is there any info we need from Felix Zweig about the Acer so that we don't run into this next time when we add support for the HP again?
It might be good to leave a comment in the source that these two conflict.
Anyway, thanks for the info.
regards,
dan carpenter