linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* New mousedev device!
@ 2002-07-04 14:03 Freeze
  2002-07-04 21:25 ` Brad Hards
  0 siblings, 1 reply; 2+ messages in thread
From: Freeze @ 2002-07-04 14:03 UTC (permalink / raw)
  To: linux-hotplug

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.

   In the hotplug device description, what is the number position that is 
used for the driver option.

Thanks,
Freeze
---
Here is an extract of the mousedev.c code: I mean, can i change the 
dev->evbit by changing the hotplug description of my device in the file 
/etc/hotplug/usb.distmap?
---
static struct input_handle *mousedev_connect(struct input_handler *handler, 
struct input_dev *dev)
{
	struct mousedev *mousedev;
	int minor = 0;

	if (!test_bit(EV_KEY, dev->evbit) ||
	   (!test_bit(BTN_LEFT, dev->keybit) && !test_bit(BTN_TOUCH, dev->keybit)))
		return NULL;

	if ((!test_bit(EV_REL, dev->evbit) || !test_bit(REL_X, dev->relbit)) &&
	    (!test_bit(EV_ABS, dev->evbit) || !test_bit(ABS_X, dev->absbit)))
		return NULL;


-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: New mousedev device!
  2002-07-04 14:03 New mousedev device! Freeze
@ 2002-07-04 21:25 ` Brad Hards
  0 siblings, 0 replies; 2+ messages in thread
From: Brad Hards @ 2002-07-04 21:25 UTC (permalink / raw)
  To: linux-hotplug

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-07-04 21:25 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-07-04 14:03 New mousedev device! Freeze
2002-07-04 21:25 ` Brad Hards

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).