[opensuse-kernel] /dev/input/mice + /dev/input/mouseX assignment?
Hi, I have an issue to setup properly a EXII Microtouch touch screen. The device is working fine, however there are 2 devices being assigned to the 1 physical touch. One /dev/input/event and one /dev/input/mouse [and naturally because of /dev/input/mouse a /dev/input/mice is created, too] The problem is that my X config has support for both a (physical mouse via) /dev/input/mice and for the touch screen found at /dev/input/event. So currently practically the touch screen is working all the time, regardless if I disable the touch input interface in the ServerLayout, as /dev/input/mice always kicks in. So my question: * Who creates the /dev/input/mouseX devices based upon the /dev/input/inputX devices in suse 10.2? As I see if mouse0 would not be created, the mice would not be created, either (at least according to the mousedev.c in the kernel source) I have tried to check the udev rules, but udev already assumes that there are mouseX devices already being assigned to. Thanks, Tibor Harsszegi -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Fri, 11 Jun 2010, Hársszegi Tibor wrote:
* Who creates the /dev/input/mouseX devices based upon the /dev/input/inputX devices in suse 10.2?
Kernel creates /dev/input/mouseX nodes for those devices which it considers to be a mouse. The creation itself happens in mousedev_create(). If you ask what input devices kernel considers to be mice, please see mousedev_ids[] in drivers/input/mousedev.c -- it describes capabilities that input device must have for kernel to consider it to be a mouse. -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
Can I do any "trick" (no clue, /usr/share/hal/fdi/policy/10osvendor/ changes) to remove the given capability so that the kernel does NOT recognize the touch as a mouse?
-----Original Message----- From: Jiri Kosina [mailto:jkosina@suse.cz] Sent: Friday, June 11, 2010 10:19 AM To: Hársszegi Tibor Cc: opensuse-kernel@opensuse.org Subject: Re: [opensuse-kernel] /dev/input/mice + /dev/input/mouseX assignment?
On Fri, 11 Jun 2010, Hársszegi Tibor wrote:
* Who creates the /dev/input/mouseX devices based upon the /dev/input/inputX devices in suse 10.2?
Kernel creates /dev/input/mouseX nodes for those devices which it considers to be a mouse. The creation itself happens in mousedev_create().
If you ask what input devices kernel considers to be mice, please see mousedev_ids[] in drivers/input/mousedev.c -- it describes capabilities that input device must have for kernel to consider it to be a mouse.
-- Jiri Kosina SUSE Labs, Novell Inc.
-- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
On Fri, 11 Jun 2010, Hársszegi Tibor wrote:
Can I do any "trick" (no clue, /usr/share/hal/fdi/policy/10osvendor/ changes) to remove the given capability so that the kernel does NOT recognize the touch as a mouse?
Not trivially (i.e. without actually chainging kernel source). What are the capabilities of the device [1], and why exactly you don't want it to be muxed to mice node? [1] relevant entry from /proc/bus/input/devices will show that -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-kernel+help@opensuse.org
participants (2)
-
Hársszegi Tibor
-
Jiri Kosina