Re: evdev and Trust TB-5300 tablet: wrong axis labels

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Dec 15, 2009 at 01:06:07AM +0200, Daniil V. Kolpakov wrote:
> В сообщении от 14 декабря 2009 Matthew Helsley написал(a):
> [...]
> > Looks like they may have re-branded the "Genius MousePen 5x4 Tablet"
> > to your "Trust TB-5300".
> [...]
> > If you search for "Genius MousePen 5x4 Tablet" or something like it
> > then perhaps you'll find more ideas for fixing your tablet.
> 
> Nothing interesting — mostly I get howtos on installing some (proprietary?) 
> driver called "wizardpen", and usually with xorg.conf instead of HAL rules.
> 
> I've tried enabling "MULTI_INPUT" quirk, as you've suggested:
> 
> [root@shinestar:~]$ modprobe -r usbhid
> [root@shinestar:~]$ modprobe usbhid "quirks=0x5543:0x0004:0x0040"
> 
> It "splitted" the tablet to three devices, as in your case:
> 
> I: Bus=0003 Vendor=5543 Product=0004 Version=0100
> N: Name="UC-LOGIC Tablet WP5540U"
> P: Phys=usb-0000:03:00.0-2/input0
> S: 
> Sysfs=/devices/pci0000:00/0000:00:06.0/0000:03:00.0/usb1/1-2/1-2:1.0/input/input15
> U: Uniq=
> H: Handlers=mouse2 event6
> B: EV=1b
> B: KEY=c01 1 0 0 0 0
> B: ABS=1000003
> B: MSC=10
> 
> I: Bus=0003 Vendor=5543 Product=0004 Version=0100
> N: Name="UC-LOGIC Tablet WP5540U"
> P: Phys=usb-0000:03:00.0-2/input0
> S: 
> Sysfs=/devices/pci0000:00/0000:00:06.0/0000:03:00.0/usb1/1-2/1-2:1.0/input/input16
> U: Uniq=
> H: Handlers=mouse3 event7
> B: EV=17
> B: KEY=70000 0 0 0 0
> B: REL=303
> B: MSC=10
> 
> I: Bus=0003 Vendor=5543 Product=0004 Version=0100
> N: Name="UC-LOGIC Tablet WP5540U"
> P: Phys=usb-0000:03:00.0-2/input0
> S: 
> Sysfs=/devices/pci0000:00/0000:00:06.0/0000:03:00.0/usb1/1-2/1-2:1.0/input/input17
> U: Uniq=
> H: Handlers=mouse4 event8
> B: EV=1b
> B: KEY=400 70000 0 0 0 0
> B: ABS=1000003
> B: MSC=10
> 
> But xinput only gets two of them. They don't send events (xinput test shows 
> this). But, looking at Xorg.0.log now, I see that the first device is hooked 
> by synaptics driver which cannot init because hardware is unsupported. I know 
> why, I've seen overriding rules in hal config. I'll try to reconfigure it to 
> use evdev driver.

synaptics kicks in after the catchall evdev configuration and overwrites it.
the reason why it overrides for this device is that anything with absolute
x/y coordinates and buttons are labelled as touchpads by HAL and the default
configurations then hook onto this label.

easiest workaround is to drop in your custom configuration into
/etc/hal/fdi/policies/ and (if you already have another one there) make sure
that it's loaded last.  HAL uses alphasort when reading the directories.

the match rule needed is something like this:

<match key="input.product" contains="U-LOGIC">
       <merge key="input.x11_driver" type="string">evdev</merge>
</match>

Cheers,
  Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux