Vojtech Pavlik wrote:
[snipped]
> Yes, it's enough to load wacom.o evdev.o mousedev.o and input.o.
> After that, the graphire will work both as a PS/2 mouse (c 13 32)
> and also via an event device (c 13 64), which then can be interfaced
> to X using a XInput module.
I've been thinking about how best to set up my newly acquired graphire.
I would like to have control over the various devices in various ways.
In particular, I would prefer that the graphire worked via the input
event interface (to an XInput driver), and was ignored by the mousedev
interface.
It would seem a useful approach to be able to select which devices were
associated with the legacy joystick and mouse interfaces, in the
transition to events.
Is there a convenient way to do this without hacking the input drivers
on a device by device basis? I know I could ignore the mousedev
interface, but I need that for the USB mouse. I also considered dumping
the mixed mice (13/63) device, and using 13/32, but with both mouse and
graphire plugged in on start, there is no assurance that the mouse will
be any particular device.
Also (or alternatively), is there a convenient way to tell which device
is connected to which event device?
Brad
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
