From: Peter Osterlund <petero2@telia.com>
To: Ricardo Galli <gallir@uib.es>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1: Synaptics driver makes touchpad unusable
Date: 16 Jul 2003 17:04:38 +0200 [thread overview]
Message-ID: <m2brvutsvt.fsf@telia.com> (raw)
In-Reply-To: <200307161649.55783.gallir@uib.es>
Ricardo Galli <gallir@uib.es> writes:
> On Tuesday 15 July 2003 23:33, Peter Osterlund shaped the electrons to shout:
> > Does it help to make the timeout even longer? (15 seconds for example)
> > Does it help to disable the reset sequence altogether, like this?
> >
> > diff -u -r -N linux-2.6.0-test1/drivers/input/mouse/synaptics.c
> > linux-tmp/drivers/input/mouse/synaptics.c ---
> > linux-2.6.0-test1/drivers/input/mouse/synaptics.c Sat Jul 12 00:17:19 2003
> > +++ linux-tmp/drivers/input/mouse/synaptics.c Tue Jul 15 23:31:01 2003 @@
> > -81,6 +81,8 @@
> > {
> > unsigned char r[2];
> >
> > + return 0;
> > +
> > if (psmouse_command(psmouse, r, PSMOUSE_CMD_RESET_BAT))
> > return -1;
> > if (r[0] == 0xAA && r[1] == 0x00)
>
>
> No, it didn't help. With the above patch, the x server gives the following
> errors:
> Query no Synaptics: 0000C8
> (EE) TouchPad no synaptics touchpad detected and no repeater device
> (EE) TouchPad Unable to query/initialize Synaptics hardware.
Looks like the wrong protocol is specified in the X driver
configuration. You must set "Device" to "/dev/input/eventX" and
"Protocol" to "event", where X is probably 0 in your case.
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2003-07-16 14:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-15 10:44 2.6.0-test1: Synaptics driver makes touchpad unusable Ricardo Galli
2003-07-15 13:04 ` Peter Osterlund
2003-07-15 15:53 ` Ricardo Galli
2003-07-15 21:33 ` Peter Osterlund
2003-07-16 14:49 ` Ricardo Galli
2003-07-16 15:04 ` Peter Osterlund [this message]
2003-07-15 19:14 ` Dax Kelson
2003-07-15 21:27 ` Peter Osterlund
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=m2brvutsvt.fsf@telia.com \
--to=petero2@telia.com \
--cc=gallir@uib.es \
--cc=linux-kernel@vger.kernel.org \
/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).