On Fri, Feb 10, 2012 at 02:00:13PM -0600, Chris Bagwell wrote: > On Fri, Feb 10, 2012 at 1:11 PM, Przemo Firszt <[email protected]> wrote: > > Dnia 2012-02-10, pią o godzinie 12:44 -0600, Chris Bagwell pisze: > >> On Fri, Feb 10, 2012 at 12:27 PM, Peter Hutterer > >> <[email protected]> wrote: > >> > On Fri, Feb 10, 2012 at 05:55:16PM +0000, Przemo Firszt wrote: > >> >> Intuos4 Wireless doesn't match list of devices in 50-wacom.conf, so > >> >> evdev was > >> >> taking over. This patch fixes it, so now wacom driver is used fo > >> >> Intuoe4 WL > >> >> PTK-540WL > >> >> > >> >> Signed-off-by: Przemo Firszt <[email protected]> > >> > > >> > out of interest - did MatchVendor work at all? > >> > >> Przemo, if you want the inside scope of what it checks, run "edevadm > >> info --export-db" and look for area that defines your > >> /dev/input/event*. The line with NAME=PTK-540WL is where the Product > >> Name came from and the the line ID_VENDOR=xxx is were I believe > >> MatchVendor gets its value. > >> > > > > Peter, Chris, > > I didn't tested it as I didn't see anything with "vendor" after > > "udevadm info --export-db". This is with "PTK-540WL" added, but (as far > > as I understand how it works) it makes no difference: > > Based on your output below, yeah, I don't think it would work either. > > > > > P: > > /devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:1/0005:056A:00BD.0002 > > E: UDEV_LOG=3 > > E: > > DEVPATH=/devices/pci0000:00/0000:00:1d.0/usb2/2-2/2-2:1.0/bluetooth/hci0/hci0:1/0005:056A:00BD.0002 > > E: DRIVER=wacom > > E: HID_ID=0005:0000056A:000000BD > > E: HID_NAME=PTK-540WL > > E: HID_PHYS=00:11:67:D6:1D:BF > > E: HID_UNIQ=00:10:60:26:58:E7 > > E: MODALIAS=hid:b0005v0000056Ap000000BD > > E: SUBSYSTEM=hid > > > > Other devices are reporting ID_VENDOR: > > > > [przemo@pldmachine ~]$ udevadm info --export-db| grep ID_VENDOR > > E: ID_VENDOR_FROM_DATABASE=Broadcom Corporation > > E: ID_VENDOR_ID=0x14e4 > > E: ID_VENDOR=ISSC > > E: ID_VENDOR_ENC=ISSC > > [..] > > > > Is it something that is worth investigation/fixing or I should just move > > on? > > I don't know enough about Bluetooth and HID behavior to know why it > doesn't return an vendor ID. The 0x56a is listed multiple times but > not always in a concatenated ID form. > > So I'm not sure what else to investigate.
yeah, same with me, not quite sure right now where to match properly. I've pushed your patch for now, if we figure out how to do it better we can amend it later. 96a2e90..4709394 master -> master Cheers, Peter ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
