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
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
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
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
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
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
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
>
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
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
>
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:
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:
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.
12 matches
Mail list logo
