From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Hards Date: Thu, 04 Jul 2002 21:25:34 +0000 Subject: Re: New mousedev device! Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Fri, 5 Jul 2002 00:03, Freeze wrote: > Hi, > I have a new device that could work with th input/mousedev driver. It is > a thrust graic tablet. But it's recognized as a relative mouse, but I'd > like to told the mousedev that it is an absolute device. /dev/input/mouseX and /dev/input/mice are inherently relative. The code that you provided basically shows that mousedev.o only tries to associate with input devices that have relative axes, and devices that have absolute X and Y axes - ie mice and touchpads. The output is always relative. Two options: 1. Use the event output driver, and manage the absolute output in userspace (eg using a X driver attached to /dev/input/eventX). There is some code in the Linuxconsole CVS, I think. 2. Use the touchpad output driver (only in linuxconsole CVS). Seen it, not looked in detail or used it. Brad -- http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Caffeinated soap. No kidding. http://thinkgeek.com/sf _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel