From: Peter Osterlund <petero2@telia.com>
To: Andreas Jellinghaus <aj@dungeon.inka.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 input drivers FAQ
Date: 01 Feb 2004 16:56:02 +0100 [thread overview]
Message-ID: <m2ekte94kt.fsf@p4.localdomain> (raw)
In-Reply-To: <pan.2004.02.01.15.25.39.951190@dungeon.inka.de>
Andreas Jellinghaus <aj@dungeon.inka.de> writes:
> And what about dell latitude laptops (synaptics touchpad - works fine -
> plus that mouse stick - no reaction at all?
>
> Usualy I'm fine with the touchpad, but some people prefer to use
> the stick or both. Any idea?
X isn't reading from /dev/input/mouse1, which is where the events for
the stick go in your case. You need to add another InputDevice to your
X config or use the /dev/input/mice device node.
> devices: (plus pcspeaker and keyboard):
> I: Bus=0011 Vendor=0002 Product=0007 Version=0000
> N: Name="SynPS/2 Synaptics TouchPad"
> P: Phys=isa0060/serio1/input0
> H: Handlers=mouse0 event1
> B: EV=b
> B: KEY=6420 0 670000 0 0 0 0 0 0 0 0
> B: ABS=11000003
>
> I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> N: Name="PS/2 Generic Mouse"
> P: Phys=synaptics-pt/serio0/input0
> H: Handlers=mouse1 event2
> B: EV=7
> B: KEY=70000 0 0 0 0 0 0 0 0
> B: REL=3
>
> XF86Config:
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "ExplorerPS/2"
> Option "Device" "/dev/input/mouse0"
> Option "Emulate3Buttons" "on"
> EndSection
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2004-02-01 15:56 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-01 10:06 2.6 input drivers FAQ Vojtech Pavlik
2004-02-01 13:15 ` Andries Brouwer
2004-02-01 13:50 ` Vojtech Pavlik
2004-02-01 15:14 ` Andries Brouwer
2004-02-02 9:35 ` Vojtech Pavlik
2004-02-02 9:43 ` Vojtech Pavlik
2004-02-01 13:51 ` Marcel J.E. Mol
2004-02-01 15:18 ` Andries Brouwer
2004-02-01 15:25 ` Andreas Jellinghaus
2004-02-01 15:56 ` Peter Osterlund [this message]
2004-02-01 16:58 ` Andreas Jellinghaus
2004-02-01 21:54 ` Vojtech Pavlik
2004-02-01 16:31 ` Joshua Kwan
2004-02-01 18:23 ` Gene Heskett
2004-02-02 16:45 ` Valdis.Kletnieks
2004-02-02 5:27 ` Valdis.Kletnieks
2004-02-02 9:23 ` Vojtech Pavlik
2004-02-02 18:12 ` Valdis.Kletnieks
2004-02-02 20:18 ` Vojtech Pavlik
2004-02-02 20:24 ` Joshua Kwan
2004-02-02 21:16 ` Vojtech Pavlik
2004-02-02 20:28 ` Valdis.Kletnieks
2004-02-02 21:19 ` Vojtech Pavlik
2004-02-02 9:24 ` Vojtech Pavlik
2004-02-02 9:29 ` Joshua Kwan
2004-02-01 21:54 ` 2.6 input drivers FAQ (ir-kbd-gpio.ko) Jose Luis Domingo Lopez
2004-02-02 10:27 ` Gerd Knorr
2004-02-16 22:42 ` Pavel Machek
2004-02-16 23:36 ` Arkadiusz Miskiewicz
2004-02-17 9:33 ` Gerd Knorr
2004-02-02 17:50 ` 2.6 input drivers FAQ Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2004-02-02 11:34 Andries.Brouwer
2004-02-02 12:25 ` Vojtech Pavlik
2004-02-02 12:44 Andries.Brouwer
2004-02-02 12:56 ` Vojtech Pavlik
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=m2ekte94kt.fsf@p4.localdomain \
--to=petero2@telia.com \
--cc=aj@dungeon.inka.de \
--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