From: Allan Sandfeld Jensen <snowwolf@one2one-networks.com>
To: linux-kernel@vger.kernel.org
Subject: Wheel mice on thinkpad ps/2
Date: Thu, 2 Aug 2001 08:51:26 +0200 [thread overview]
Message-ID: <20010802065332Z268824-28344+348@vger.kernel.org> (raw)
I think this message didnt reach the mailing-list the first time, trying
again.
Sorry if you see this message twice.
---------- Forwarded Message ----------
Hi.
I've solved a long standing problem with using an extended mouse over the
ps/2 port on a thinkpad. (search deja, I found bugreports dating back to
1998, all unanswered)
I discovered there is a "smart" device called a trackpoint controller, that
accumulates movement from both the trackpoints and the external mouse.
Provided it understands the external mouse! (it only understand standard
mice) A quick hack is disabling the trackpoint controller by sending 0xe2
0x4e, but a more general solution would be to write a linux driver that
autodetected a trackpoint controller with external mouse and disabled it. In
that way it would be transparant to userspace drivers.
The easiest for my would be writing it into pc_keyb.c but that's not
appropiate. So where should I place the driver?
If I want advanced functionality, where I instead demultiplexes the
trackpoint and the external mouse into a /dev/psaux1 and -2, I need to take
over the aux interrupthandler. Otherwise I can just speak through the
standard psaux.
And what of the new input-class, should all inputdevices eventually move over
there, or just USB?
regards
-Allan
-------------------------------------------------------
next reply other threads:[~2001-08-02 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 6:51 Allan Sandfeld Jensen [this message]
2001-08-02 14:10 ` James Simmons
-- strict thread matches above, loose matches on Subject: below --
2001-08-01 9:13 Allan Sandfeld Jensen
2001-08-01 22:28 ` Thomas Hood
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=20010802065332Z268824-28344+348@vger.kernel.org \
--to=snowwolf@one2one-networks.com \
--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
all inboxes | Powered by JetHome®