remapping XInput axes

Peter Hutterer peter.hutterer at who-t.net
Mon Oct 24 18:06:26 PDT 2011


On Mon, Oct 24, 2011 at 01:59:50PM +0200, Tamas Papp wrote:
> On Mon, 24 Oct 2011, Peter Hutterer wrote:
> 
> > On Fri, Oct 21, 2011 at 02:45:06PM +0200, Tamas Papp wrote:
> > > Hi,
> > > 
> > > I just purchased an Intellipen Pro digital pen.  It shows up fine in
> > > xinput list:
> > 
> > 
> > [...]
> > > 
> > > and button events are detected, but the cursor doesn't move. xinput
> > > test reveals that the X and Y axes are a[2] and a[3]:
> > 
> > [...]
> > 
> > > Device 'EPOS EPOS Pen Digitizer.':
> > > 	Device Enabled (132):	1
> > > 	Coordinate Transformation Matrix (134):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
> > > 	Device Accel Profile (257):	0
> > > 	Device Accel Constant Deceleration (258):	1.000000
> > > 	Device Accel Adaptive Deceleration (259):	1.000000
> > > 	Device Accel Velocity Scaling (260):	10.000000
> > > 	Evdev Axis Inversion (261):	0, 0
> > > 	Evdev Axis Calibration (262):	<no items>
> > > 	Evdev Axes Swap (263):	0
> > > 	Axis Labels (264):	"Abs X" (254), "Abs Y" (255), "Abs Z" (275), "Abs Rotary X" (276), "Abs Pressure" (485), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285), "Abs Misc" (285)
> > 
> > 
> > Fairly common issue. The kernel needs a fix to enable HID_QUIRK_MULTI_INPUT
> > for this device.
> 
> Hi Peter,
> 
> Thanks, that put me on the right track.  I just had to create
> 
> /etc/hal/fdi/policy/90-intellipen-pro.fdi
> 
> with the contents
> 
> <?xml version="1.0" encoding="UTF-8"?>
> 
> <deviceinfo version="0.2">
> 
>   <device>
>     <!-- Intellipen Pro -->
>     <match key="usb_device.vendor_id" int="0x188c">
>       <match key="usb_device.product_id" int="0x221">
> 	<merge key="input.x11_driver" type="string">evdev</merge>
>       </match>
>     </match>
>   </device>
> 
> </deviceinfo>
> 
> and 
> 
> /etc/modprobe.d/intellipen.conf
> 
> with
> 
> options usbhid "quirks=0x188c:0x0221:0x0040"
> 
> and the device works perfectly.  Where should I submit this
> information so that it gets incorporated to future updates so that
> others can just plug it in and have it work automatically?

kernel bugzilla. I'd be easy enough to knock up a kernel patch that adds the
quirk for this particular device, so if you can find the time to do that
you're most likely to see the change happen.

Cheers,
  Peter



More information about the xorg mailing list