Re: ALPS tapping disabled. WHY?
On Tue, Mar 01, 2005 at 06:40:21AM -0500, David Ford wrote: > I would also appreciate the return of good resolution. Blocky mouse > startup moves make graphic editing rather difficult. No mouse movement > until I have moved my finger a significant distance then the mouse all > of a sudden jumps a dozen pixels before it "smoothly" glides along. > > I would also love to see the sync issues go away. :/ Whatever this > patch(es) was supposed to accomplish, it introduced some rather > undesirable side effects. a) sync issues, b) tapping, c) fine grain > movements, d) loss of scroll sliding as well (moving your finger along > the side/bottom of the glidepoint). > > Not griping, just providing feedback. Can you check with a current -mm kernel whether any of the issues is still there? Everything seems to work smoothly with my ALPS. -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
I would also appreciate the return of good resolution. Blocky mouse startup moves make graphic editing rather difficult. No mouse movement until I have moved my finger a significant distance then the mouse all of a sudden jumps a dozen pixels before it "smoothly" glides along. I would also love to see the sync issues go away. :/ Whatever this patch(es) was supposed to accomplish, it introduced some rather undesirable side effects. a) sync issues, b) tapping, c) fine grain movements, d) loss of scroll sliding as well (moving your finger along the side/bottom of the glidepoint). Not griping, just providing feedback. -david Ian E. Morgan wrote: On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
I would also appreciate the return of good resolution. Blocky mouse startup moves make graphic editing rather difficult. No mouse movement until I have moved my finger a significant distance then the mouse all of a sudden jumps a dozen pixels before it smoothly glides along. I would also love to see the sync issues go away. :/ Whatever this patch(es) was supposed to accomplish, it introduced some rather undesirable side effects. a) sync issues, b) tapping, c) fine grain movements, d) loss of scroll sliding as well (moving your finger along the side/bottom of the glidepoint). Not griping, just providing feedback. -david Ian E. Morgan wrote: On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Tue, Mar 01, 2005 at 06:40:21AM -0500, David Ford wrote: I would also appreciate the return of good resolution. Blocky mouse startup moves make graphic editing rather difficult. No mouse movement until I have moved my finger a significant distance then the mouse all of a sudden jumps a dozen pixels before it smoothly glides along. I would also love to see the sync issues go away. :/ Whatever this patch(es) was supposed to accomplish, it introduced some rather undesirable side effects. a) sync issues, b) tapping, c) fine grain movements, d) loss of scroll sliding as well (moving your finger along the side/bottom of the glidepoint). Not griping, just providing feedback. Can you check with a current -mm kernel whether any of the issues is still there? Everything seems to work smoothly with my ALPS. -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan -- --- Ian E. Morgan Vice President & C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Sun, 27 Feb 2005, Vojtech Pavlik wrote: Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). You should really try to get that squeezed into 2.6.11 before it is released, or else I would anticipate a LOT more people whining about their broken touchpads. Regards, Ian Morgan -- --- Ian E. Morgan Vice President C.O.O. Webcon, Inc. imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca * Customized Linux Network Solutions for your Business * --- - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Thu, Feb 24, 2005 at 10:08:15PM -0500, Dmitry Torokhov wrote: > > So now, can anyone explain what bit 3 of param[0] does, and why you would > > want to disable hardware tapping support when it's set? My pad (ALPS > > 56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a > > plain PS/2 mouse, no special ALPS support req'd. > > > > Can this disabling of hardware tapping support be made optional (boot time > > param or other)? I don't want to have to patch every kernel from here on > > out. > > > > It still should do software tap emulation (although support is a bit flakey > with ALPS I must admit, but there are patches that should improve it) - so > people who don't like tapping can deactivate it. > > Anyway, "psmouse.proto=exps" boot option should disable ALPS native mode and > restore previous behavior. Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Thu, Feb 24, 2005 at 10:08:15PM -0500, Dmitry Torokhov wrote: So now, can anyone explain what bit 3 of param[0] does, and why you would want to disable hardware tapping support when it's set? My pad (ALPS 56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a plain PS/2 mouse, no special ALPS support req'd. Can this disabling of hardware tapping support be made optional (boot time param or other)? I don't want to have to patch every kernel from here on out. It still should do software tap emulation (although support is a bit flakey with ALPS I must admit, but there are patches that should improve it) - so people who don't like tapping can deactivate it. Anyway, psmouse.proto=exps boot option should disable ALPS native mode and restore previous behavior. Also, in my tree currently (and planned for 2.6.12) hardware tapping is enabled again, because double taps don't work otherwise (hardware limitation). -- Vojtech Pavlik SuSE Labs, SuSE CR - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Thursday 24 February 2005 18:29, Ian E. Morgan wrote:
> Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
> reading several threads related to the topic, noe seemed to resolve my
> issue.
>
> The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
> 2.6.10.
>
> This change fixes the problem by NOT disabling hardware tapping:
>
> --- linux-2.6.11-rc5/drivers/input/mouse/alps.c~ 2005-02-24
> 18:16:03.0 -0500
> +++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24
> 18:16:03.0 -0500
> @@ -334,8 +334,8 @@
> if (alps_get_status(psmouse, param))
> return -1;
>
> - if (param[0] & 0x04)
> - alps_tap_mode(psmouse, 0);
> +// if (param[0] & 0x04)
> +// alps_tap_mode(psmouse, 0);
>
> if (alps_absolute_mode(psmouse)) {
> printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
> @@ -372,11 +372,11 @@
> return -1;
> }
>
> - if (param[0] & 0x04) {
> - printk(KERN_INFO " Disabling hardware tapping\n");
> - if (alps_tap_mode(psmouse, 0))
> - printk(KERN_WARNING "alps.c: Failed to disable hardware
> tapping\n");
> - }
> +// if (param[0] & 0x04) {
> +// printk(KERN_INFO " Disabling hardware tapping\n");
> +// if (alps_tap_mode(psmouse, 0))
> +// printk(KERN_WARNING "alps.c: Failed to disable hardware
> tapping\n");
> +// }
>
> if (alps_absolute_mode(psmouse)) {
> printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
>
>
>
> So now, can anyone explain what bit 3 of param[0] does, and why you would
> want to disable hardware tapping support when it's set? My pad (ALPS
> 56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
> plain PS/2 mouse, no special ALPS support req'd.
>
> Can this disabling of hardware tapping support be made optional (boot time
> param or other)? I don't want to have to patch every kernel from here on
> out.
>
It still should do software tap emulation (although support is a bit flakey
with ALPS I must admit, but there are patches that should improve it) - so
people who don't like tapping can deactivate it.
Anyway, "psmouse.proto=exps" boot option should disable ALPS native mode and
restore previous behavior.
--
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ALPS tapping disabled. WHY?
Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
reading several threads related to the topic, noe seemed to resolve my
issue.
The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
2.6.10.
This change fixes the problem by NOT disabling hardware tapping:
--- linux-2.6.11-rc5/drivers/input/mouse/alps.c~2005-02-24
18:16:03.0 -0500
+++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24 18:16:03.0
-0500
@@ -334,8 +334,8 @@
if (alps_get_status(psmouse, param))
return -1;
- if (param[0] & 0x04)
- alps_tap_mode(psmouse, 0);
+// if (param[0] & 0x04)
+// alps_tap_mode(psmouse, 0);
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
@@ -372,11 +372,11 @@
return -1;
}
- if (param[0] & 0x04) {
- printk(KERN_INFO " Disabling hardware tapping\n");
- if (alps_tap_mode(psmouse, 0))
- printk(KERN_WARNING "alps.c: Failed to disable hardware
tapping\n");
- }
+// if (param[0] & 0x04) {
+// printk(KERN_INFO " Disabling hardware tapping\n");
+// if (alps_tap_mode(psmouse, 0))
+// printk(KERN_WARNING "alps.c: Failed to disable hardware
tapping\n");
+// }
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR "alps.c: Failed to enable absolute mode\n");
So now, can anyone explain what bit 3 of param[0] does, and why you would
want to disable hardware tapping support when it's set? My pad (ALPS
56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
plain PS/2 mouse, no special ALPS support req'd.
Can this disabling of hardware tapping support be made optional (boot time
param or other)? I don't want to have to patch every kernel from here on
out.
Regards,
Ian Morgan
--
---
Ian E. Morgan Vice President & C.O.O. Webcon, Inc.
imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca
* Customized Linux Network Solutions for your Business *
---
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
ALPS tapping disabled. WHY?
Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
reading several threads related to the topic, noe seemed to resolve my
issue.
The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
2.6.10.
This change fixes the problem by NOT disabling hardware tapping:
--- linux-2.6.11-rc5/drivers/input/mouse/alps.c~2005-02-24
18:16:03.0 -0500
+++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24 18:16:03.0
-0500
@@ -334,8 +334,8 @@
if (alps_get_status(psmouse, param))
return -1;
- if (param[0] 0x04)
- alps_tap_mode(psmouse, 0);
+// if (param[0] 0x04)
+// alps_tap_mode(psmouse, 0);
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
@@ -372,11 +372,11 @@
return -1;
}
- if (param[0] 0x04) {
- printk(KERN_INFO Disabling hardware tapping\n);
- if (alps_tap_mode(psmouse, 0))
- printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
- }
+// if (param[0] 0x04) {
+// printk(KERN_INFO Disabling hardware tapping\n);
+// if (alps_tap_mode(psmouse, 0))
+// printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
+// }
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
So now, can anyone explain what bit 3 of param[0] does, and why you would
want to disable hardware tapping support when it's set? My pad (ALPS
56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
plain PS/2 mouse, no special ALPS support req'd.
Can this disabling of hardware tapping support be made optional (boot time
param or other)? I don't want to have to patch every kernel from here on
out.
Regards,
Ian Morgan
--
---
Ian E. Morgan Vice President C.O.O. Webcon, Inc.
imorgan at webcon dot ca PGP: #2DA40D07 www.webcon.ca
* Customized Linux Network Solutions for your Business *
---
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: ALPS tapping disabled. WHY?
On Thursday 24 February 2005 18:29, Ian E. Morgan wrote:
Trying out 2.6.11-rc5, I discovered my ALPS touchpad misbehaving. After
reading several threads related to the topic, noe seemed to resolve my
issue.
The pad has always worked fine as a plain PS/2 mouse, from 2.4.0 through
2.6.10.
This change fixes the problem by NOT disabling hardware tapping:
--- linux-2.6.11-rc5/drivers/input/mouse/alps.c~ 2005-02-24
18:16:03.0 -0500
+++ linux-2.6.11-rc5/drivers/input/mouse/alps.c 2005-02-24
18:16:03.0 -0500
@@ -334,8 +334,8 @@
if (alps_get_status(psmouse, param))
return -1;
- if (param[0] 0x04)
- alps_tap_mode(psmouse, 0);
+// if (param[0] 0x04)
+// alps_tap_mode(psmouse, 0);
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
@@ -372,11 +372,11 @@
return -1;
}
- if (param[0] 0x04) {
- printk(KERN_INFO Disabling hardware tapping\n);
- if (alps_tap_mode(psmouse, 0))
- printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
- }
+// if (param[0] 0x04) {
+// printk(KERN_INFO Disabling hardware tapping\n);
+// if (alps_tap_mode(psmouse, 0))
+// printk(KERN_WARNING alps.c: Failed to disable hardware
tapping\n);
+// }
if (alps_absolute_mode(psmouse)) {
printk(KERN_ERR alps.c: Failed to enable absolute mode\n);
So now, can anyone explain what bit 3 of param[0] does, and why you would
want to disable hardware tapping support when it's set? My pad (ALPS
56AAA1760C on a Sager NP8560V) has always worked with hardware tapping as a
plain PS/2 mouse, no special ALPS support req'd.
Can this disabling of hardware tapping support be made optional (boot time
param or other)? I don't want to have to patch every kernel from here on
out.
It still should do software tap emulation (although support is a bit flakey
with ALPS I must admit, but there are patches that should improve it) - so
people who don't like tapping can deactivate it.
Anyway, psmouse.proto=exps boot option should disable ALPS native mode and
restore previous behavior.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
