From: Vojtech Pavlik <vojtech@suse.cz>
To: Peter Osterlund <petero2@telia.com>
Cc: Pete Zaitcev <zaitcev@redhat.com>,
linux-kernel@vger.kernel.org, dtor_core@ameritech.net
Subject: Re: Touchpad problems with 2.6.11-rc2
Date: Fri, 4 Feb 2005 14:25:32 +0100 [thread overview]
Message-ID: <20050204132532.GH10424@ucw.cz> (raw)
In-Reply-To: <m38y64x1xw.fsf@telia.com>
On Fri, Feb 04, 2005 at 07:40:43AM +0100, Peter Osterlund wrote:
> Vojtech Pavlik <vojtech@suse.cz> writes:
>
> > On Thu, Feb 03, 2005 at 10:54:51PM +0100, Peter Osterlund wrote:
> >
> > > * Removes the xres/yres scaling so that you get the same speed in the
> > > X and Y directions even if your screen is not square.
> >
> > The old code assumed that both the pad and the screen are 4:3, not
> > square. It was wrong still.
>
> alps.c currently contains:
>
> psmouse->dev.evbit[LONG(EV_ABS)] |= BIT(EV_ABS);
> input_set_abs_params(&psmouse->dev, ABS_X, 0, 1023, 0, 0);
> input_set_abs_params(&psmouse->dev, ABS_Y, 0, 1023, 0, 0);
> input_set_abs_params(&psmouse->dev, ABS_PRESSURE, 0, 127, 0, 0);
>
> Maybe it should set the ABS_Y max value to 767 in that case.
Applied.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-02-04 13:30 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-24 3:01 Touchpad problems with 2.6.11-rc2 Pete Zaitcev
2005-01-30 11:10 ` Peter Osterlund
2005-01-31 23:15 ` Pete Zaitcev
2005-02-01 3:40 ` Dmitry Torokhov
2005-02-01 5:06 ` Pete Zaitcev
2005-02-01 5:14 ` Dmitry Torokhov
2005-02-03 11:18 ` Giuseppe Bilotta
2005-02-02 7:41 ` Pete Zaitcev
2005-02-02 10:20 ` Vojtech Pavlik
2005-02-02 15:51 ` Dmitry Torokhov
2005-02-02 15:57 ` Vojtech Pavlik
2005-02-02 16:56 ` Pete Zaitcev
2005-02-02 17:07 ` Vojtech Pavlik
2005-02-02 17:58 ` Pete Zaitcev
2005-02-02 19:11 ` Vojtech Pavlik
2005-02-02 19:39 ` Pete Zaitcev
2005-02-02 19:55 ` Vojtech Pavlik
2005-02-02 19:39 ` Dmitry Torokhov
2005-02-03 8:30 ` Alexandre Oliva
2005-02-03 8:49 ` Vojtech Pavlik
2005-02-03 15:17 ` Alexandre Oliva
2005-02-03 15:28 ` Dmitry Torokhov
2005-02-03 15:45 ` Vojtech Pavlik
2005-02-02 20:57 ` Peter Osterlund
2005-02-02 21:17 ` Dmitry Torokhov
2005-02-02 21:47 ` Peter Osterlund
2005-02-02 22:06 ` Dmitry Torokhov
2005-02-02 22:27 ` Peter Osterlund
2005-02-03 7:16 ` Dmitry Torokhov
2005-02-02 21:37 ` David Ford
2005-02-02 22:11 ` Pete Zaitcev
2005-02-02 22:58 ` Peter Osterlund
2005-02-03 6:46 ` Vojtech Pavlik
2005-02-03 21:54 ` Peter Osterlund
2005-02-04 6:17 ` Vojtech Pavlik
2005-02-04 6:40 ` Peter Osterlund
2005-02-04 6:53 ` Vojtech Pavlik
2005-02-04 7:33 ` Peter Osterlund
2005-02-04 13:25 ` Vojtech Pavlik [this message]
2005-02-04 13:23 ` Vojtech Pavlik
2005-02-03 6:59 ` Pete Zaitcev
2005-01-25 19:55 David Brownell
2005-01-25 21:30 ` Dmitry Torokhov
2005-01-30 11:20 ` Peter Osterlund
2005-01-30 20:59 ` David Brownell
2005-01-31 21:46 ` Pete Zaitcev
2005-01-31 22:00 ` Dmitry Torokhov
2005-02-08 10:55 Stephane Raimbault
2005-02-08 17:05 ` Peter Osterlund
2005-02-09 8:47 ` Stephane Raimbault
2005-02-09 18:09 ` Peter Osterlund
2005-02-10 8:32 ` Stephane Raimbault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050204132532.GH10424@ucw.cz \
--to=vojtech@suse.cz \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
--cc=zaitcev@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).