From: Thomas Molina <tmolina@copper.net>
To: "P. Christeas" <p_christ@hol.gr>
Cc: Arkadiusz Miskiewicz <arekm@pld-linux.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Synaptics support kills my mouse
Date: Sun, 29 Jun 2003 12:44:56 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0306291241220.1007-100000@lap.molina> (raw)
In-Reply-To: <200306261746.14578.p_christ@hol.gr>
On Thu, 26 Jun 2003, P. Christeas wrote:
> It is true, 2.5.73 unconditionally detects and tries to use the Syn. Touchpad
> in 'absolute mode'. I wouldn't blame the authors of the module, however. They
> are already doing a great job :).
>
> I 've read the code to see what's wrong and found that the problem is that the
> Touchpad itself doesn't report any data to the PS/2 port. The code still
> looks conforming to the specs.
> However, you shouldn't give up 2.5.73 because of that. You can still use the
> PS/2 compatibility mode
> o Compile the ps mouse as a module "psmouse"
> o Arrange so that the module is loaded with the option "psmouse_noext=1"
> o Have gpm and X (you can even use both of them) read /dev/input/mice as an
> exps2 or imps2 mouse (Intellimouse Explorer PS/2) .
Further update. I can get the same effect/workaround by making the mouse
support built in (my preference) and specifying the above option on the
kernel options line.
next prev parent reply other threads:[~2003-06-29 16:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 14:46 Synaptics support kills my mouse P. Christeas
2003-06-28 1:26 ` Thomas Molina
2003-06-29 18:44 ` Thomas Molina [this message]
2003-06-30 14:37 ` P. Christeas
-- strict thread matches above, loose matches on Subject: below --
2003-06-26 1:06 Thomas Molina
2003-06-26 10:45 ` Arkadiusz Miskiewicz
2003-06-26 18:57 ` Ken Witherow
2003-06-26 17:07 ` Alessandro Suardi
2003-06-26 0:34 Thomas Molina
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=Pine.LNX.4.44.0306291241220.1007-100000@lap.molina \
--to=tmolina@copper.net \
--cc=arekm@pld-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=p_christ@hol.gr \
/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).