From: "E.Rodichev" <er@sai.msu.su>
To: linux-kernel@vger.kernel.org
Subject: /dev/psaux problem (2.6.5)
Date: Tue, 20 Apr 2004 04:26:20 +0400 (MSD) [thread overview]
Message-ID: <Pine.GSO.4.58.0404200404360.22353@ra.sai.msu.su> (raw)
Hi,
as it was described already, the new 2.6.0 approach for handling some
input devices (mice!) lead to many troubles. As for me, the tp4d daemon
(which is for IBM ThinkPad trackpoint) is very useful and reliable with
2.0, 2.2 and 2.4 kernels, but it doesn't work with 2.6.x.
There is a good problem description at
http://www.informatik.uni-freiburg.de/~danlee/fun/psaux/ and a user space
driver which solves the problem. It works fine with 2.6.3, but not with
2.6.5.
The reason is that in 2.6.5 it looks impossible to disable the existing
mouse driver, which conflicts with driver from Tuukka Toivonen. My
temporary solution was as follows:
--- drivers/input/Kconfig.orig 2004-04-04 07:36:18.000000000 +0400
+++ drivers/input/Kconfig 2004-04-20 03:45:31.000000000 +0400
@@ -26,7 +26,6 @@ comment "Userland interfaces"
config INPUT_MOUSEDEV
tristate "Mouse interface" if EMBEDDED
- default y
depends on INPUT
---help---
Say Y here if you want your mouse to be accessible as char devices
I am not experienced with the modern config managment, but it looks like
a bug in 2.6.5 configuration system. I suggest also to include Tuukka Toivonen
driver in 2.6.x tree, as it is stable, clearly described, and it solves
many compatibility problems.
_________________________________________________________________________
Evgeny Rodichev Sternberg Astronomical Institute
email: er@sai.msu.su Moscow State University
Phone: 007 (095) 939 2383
Fax: 007 (095) 932 8841 http://www.sai.msu.su/~er
next reply other threads:[~2004-04-20 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-20 0:26 E.Rodichev [this message]
2004-04-20 12:35 ` Dmitry Torokhov
2004-04-20 14:11 ` E.Rodichev
2004-04-21 3:19 ` Dmitry Torokhov
2004-04-20 7:20 Sau Dan Lee
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.GSO.4.58.0404200404360.22353@ra.sai.msu.su \
--to=er@sai.msu.su \
--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®