Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
On Sat, Feb 11, 2012 at 7:52 AM, Peter Hutterer wrote: > On Sat, Feb 11, 2012 at 11:24:15AM +, Przemo Firszt wrote: >> Wacom4 WL on usb cable - "Wacom" is part of the name, but ID_VENDOR >> field contains "Tablet" 8-): >> >> P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 >> E: UDEV_LOG=3 >> E: >> DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 >> E: PRODUCT=3/56a/bc/127 >> E: NAME="Wacom Intuos4 WL" >> E: PROP=1 >> E: EV=1f >> E: KEY=1cdf 0 1f01ff 0 0 0 0 0 0 0 0 >> E: REL=100 >> E: ABS=100 f000167 >> E: MSC=1 >> E: >> MODALIAS=input:b0003v056Ap00BCe0127-e0,1,2,3,4,k100,101,102,103,104,105,106,107,108,110,111,112,113,114,140,141,142,143,144,146,147,14A,14B,14C,r8,a0,1,2,5,6,8,18,19,1A,1B,28,m0,lsfw >> E: SUBSYSTEM=input >> E: ID_INPUT=1 >> E: ID_INPUT_TABLET=1 >> E: ID_VENDOR=Tablet >> E: ID_VENDOR_ENC=Tablet >> E: ID_VENDOR_ID=056a >> E: ID_MODEL=PTK-540WL >> E: ID_MODEL_ENC=PTK-540WL >> E: ID_MODEL_ID=00bc >> E: ID_REVISION=0127 >> E: ID_SERIAL=Tablet_PTK-540WL_00-10-60-26-58-e7 >> E: ID_SERIAL_SHORT=00-10-60-26-58-e7 >> E: ID_TYPE=hid >> E: ID_BUS=usb >> E: ID_USB_INTERFACES=:030102: >> E: ID_USB_INTERFACE_NUM=00 >> E: ID_USB_DRIVER=wacom >> E: ID_PATH=pci-:00:1d.0-usb-0:1:1.0 >> E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_1_0 >> >> Some of the kernel drivers are cheanging device name, so we could >> possibly do the same. Example here: >> drivers/hid/hid-hyperv.c: sprintf(hid_dev->name, "%s", "Microsoft >> Vmbus HID-compliant Mouse"); >> >> but it's a workaround and I think it's not worth to do it. > > I think it's worth it. the ID_VENDOR_ID is 0x56a which is Wacom, the string > should reflect this to make userspace simpler. And adding this is aligned with wacom_sys.c. It is doing same dev->name update and why you see Wacom in your output: E: NAME="Wacom Intuos4 WL" > > 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
On Sat, Feb 11, 2012 at 11:24:15AM +, Przemo Firszt wrote: > Wacom4 WL on usb cable - "Wacom" is part of the name, but ID_VENDOR > field contains "Tablet" 8-): > > P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 > E: UDEV_LOG=3 > E: > DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 > E: PRODUCT=3/56a/bc/127 > E: NAME="Wacom Intuos4 WL" > E: PROP=1 > E: EV=1f > E: KEY=1cdf 0 1f01ff 0 0 0 0 0 0 0 0 > E: REL=100 > E: ABS=100 f000167 > E: MSC=1 > E: > MODALIAS=input:b0003v056Ap00BCe0127-e0,1,2,3,4,k100,101,102,103,104,105,106,107,108,110,111,112,113,114,140,141,142,143,144,146,147,14A,14B,14C,r8,a0,1,2,5,6,8,18,19,1A,1B,28,m0,lsfw > E: SUBSYSTEM=input > E: ID_INPUT=1 > E: ID_INPUT_TABLET=1 > E: ID_VENDOR=Tablet > E: ID_VENDOR_ENC=Tablet > E: ID_VENDOR_ID=056a > E: ID_MODEL=PTK-540WL > E: ID_MODEL_ENC=PTK-540WL > E: ID_MODEL_ID=00bc > E: ID_REVISION=0127 > E: ID_SERIAL=Tablet_PTK-540WL_00-10-60-26-58-e7 > E: ID_SERIAL_SHORT=00-10-60-26-58-e7 > E: ID_TYPE=hid > E: ID_BUS=usb > E: ID_USB_INTERFACES=:030102: > E: ID_USB_INTERFACE_NUM=00 > E: ID_USB_DRIVER=wacom > E: ID_PATH=pci-:00:1d.0-usb-0:1:1.0 > E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_1_0 > > Some of the kernel drivers are cheanging device name, so we could > possibly do the same. Example here: > drivers/hid/hid-hyperv.c: sprintf(hid_dev->name, "%s", "Microsoft > Vmbus HID-compliant Mouse"); > > but it's a workaround and I think it's not worth to do it. I think it's worth it. the ID_VENDOR_ID is 0x56a which is Wacom, the string should reflect this to make userspace simpler. 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
Wacom4 WL on usb cable - "Wacom" is part of the name, but ID_VENDOR field contains "Tablet" 8-): P: /devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 E: UDEV_LOG=3 E: DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1:1.0/input/input10 E: PRODUCT=3/56a/bc/127 E: NAME="Wacom Intuos4 WL" E: PROP=1 E: EV=1f E: KEY=1cdf 0 1f01ff 0 0 0 0 0 0 0 0 E: REL=100 E: ABS=100 f000167 E: MSC=1 E: MODALIAS=input:b0003v056Ap00BCe0127-e0,1,2,3,4,k100,101,102,103,104,105,106,107,108,110,111,112,113,114,140,141,142,143,144,146,147,14A,14B,14C,r8,a0,1,2,5,6,8,18,19,1A,1B,28,m0,lsfw E: SUBSYSTEM=input E: ID_INPUT=1 E: ID_INPUT_TABLET=1 E: ID_VENDOR=Tablet E: ID_VENDOR_ENC=Tablet E: ID_VENDOR_ID=056a E: ID_MODEL=PTK-540WL E: ID_MODEL_ENC=PTK-540WL E: ID_MODEL_ID=00bc E: ID_REVISION=0127 E: ID_SERIAL=Tablet_PTK-540WL_00-10-60-26-58-e7 E: ID_SERIAL_SHORT=00-10-60-26-58-e7 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030102: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=wacom E: ID_PATH=pci-:00:1d.0-usb-0:1:1.0 E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_1_0 Some of the kernel drivers are cheanging device name, so we could possibly do the same. Example here: drivers/hid/hid-hyperv.c: sprintf(hid_dev->name, "%s", "Microsoft Vmbus HID-compliant Mouse"); but it's a workaround and I think it's not worth to do it. -- Regards, Przemo -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
On Fri, Feb 10, 2012 at 1:23 PM, Przemo Firszt wrote: > Dnia 2012-02-10, pią o godzinie 12:39 -0600, Chris Bagwell pisze: > [..] >> It would be better to have a new rule that matches Vendor name. >> >> Section "InputClass" >> Identifier "Wacom Vendor class" >> MatchVendor "Wacom" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> EndSection >> >> For "wacom" USB kernel driver, the phrase "Wacom" is hard coded into >> Product name in by driver and it ignores the Product field from HW. >> If it came purely from USB, it would look just like your seeing. For >> example, the Product value in USB Device Descriptor for my Bamboo >> shows "CTH-670". >> > [..] > Chris, > Can you check if your tablet reports ID_VENDOR? > > Full attribute walk for Intuos4 WL: http://pastebin.com/nj8qgKk4 > Vendor is not reported. Yes, here is section for my Bamboo: P: /devices/pci:00/:00:02.0/usb2/2-1/2-1:1.0/input/input63 E: UDEV_LOG=3 E: DEVPATH=/devices/pci:00/:00:02.0/usb2/2-1/2-1:1.0/input/input63 E: PRODUCT=3/56a/df/100 E: NAME="Wacom Bamboo 16FG 6x8 Pen" E: PROP=1 E: EV=b E: KEY=1c03 0 0 0 0 0 0 0 0 0 0 E: ABS=303 E: MODALIAS=input:b0003v056Ap00DFe0100-e0,1,3,k140,141,14A,14B,14C,ra0,1,18,19,mlsfw E: SUBSYSTEM=input E: ID_INPUT=1 E: ID_INPUT_TABLET=1 E: ID_VENDOR=Wacom_Co._Ltd. E: ID_VENDOR_ENC=Wacom\x20Co.\x2cLtd. E: ID_VENDOR_ID=056a E: ID_MODEL=CTH-670 E: ID_MODEL_ENC=CTH-670 E: ID_MODEL_ID=00df E: ID_REVISION=0100 E: ID_SERIAL=Wacom_Co._Ltd._CTH-670 E: ID_TYPE=hid E: ID_BUS=usb E: ID_USB_INTERFACES=:030102:03: E: ID_USB_INTERFACE_NUM=00 E: ID_USB_DRIVER=wacom E: ID_PATH=pci-:00:02.0-usb-0:1:1.0 E: ID_PATH_TAG=pci-_00_02_0-usb-0_1_1_0 E: ID_FOR_SEAT=input-pci-_00_02_0-usb-0_1_1_0 E: TAGS=:seat: Chris -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
Dnia 2012-02-10, pią o godzinie 12:39 -0600, Chris Bagwell pisze: [..] > It would be better to have a new rule that matches Vendor name. > > Section "InputClass" > Identifier "Wacom Vendor class" > MatchVendor "Wacom" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection > > For "wacom" USB kernel driver, the phrase "Wacom" is hard coded into > Product name in by driver and it ignores the Product field from HW. > If it came purely from USB, it would look just like your seeing. For > example, the Product value in USB Device Descriptor for my Bamboo > shows "CTH-670". > [..] Chris, Can you check if your tablet reports ID_VENDOR? Full attribute walk for Intuos4 WL: http://pastebin.com/nj8qgKk4 Vendor is not reported. -- Regards, Przemo -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
On Fri, Feb 10, 2012 at 11:54 AM, Przemo Firszt wrote: > Dnia 2012-02-11, sob o godzinie 03:27 +1000, Peter Hutterer pisze: >> On Fri, Feb 10, 2012 at 04:56:11PM +, Przemo Firszt wrote: >> > I was trying to find out why "xsetwacom --list devices" shows nothing >> > and I found that my tablet is being handled by evdev. >> > Details here: http://pastebin.com/jASCqiKC >> > >> > I can't see any "blacklisted devices" list in evdev, so I could exclude >> > it nor I can see anything wrong in xorg driver for wacom (it's the same >> > as for Graphire4 Bluetooth and for that one xsetwacom worked). >> > >> > Any ideas where to look for solution? >> >> /usr/share/X11/xorg.conf/d/50-wacom.conf on my machine matches mainly >> against "Wacom" in the product name - that's missing on this device. Try >> using MatchVendor, provided that contains a string that's matchable. >> If so, pls let us know so we can update the .conf file. >> > Hi Peter, > Spot on, 10/10, bull's-eye and the main prize :-) > >> [przemo@pldmachine ~]$ head /usr/share/X11/xorg.conf.d/50-wacom.conf >> Section "InputClass" >> Identifier "Wacom class" >> MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> EndSection >> >> Section "InputClass" >> Identifier "Wacom serial class" >> MatchProduct "Serial Wacom Tablet" > > I added PTK-540WL to MatchProduct. I'm not sure if that's the best way, but > it's > hard to decide without knowing how other wacom devices are called. > Patch on the way in a next 5 minutes. > > Thanks!! :-) It would be better to have a new rule that matches Vendor name. Section "InputClass" Identifier "Wacom Vendor class" MatchVendor "Wacom" MatchDevicePath "/dev/input/event*" Driver "wacom" EndSection For "wacom" USB kernel driver, the phrase "Wacom" is hard coded into Product name in by driver and it ignores the Product field from HW. If it came purely from USB, it would look just like your seeing. For example, the Product value in USB Device Descriptor for my Bamboo shows "CTH-670". For "wacom_w801" serial touchscreen driver, "Wacom" is also hard coding Product name in driver. hid-wacom is doing the reasonable thing of letting the base HID logic set the Vendor and Product values from HID report. I think its safe to assume Vendor will always be "Wacom Co., Ltd" for Wacoms since there are little options on were to get that info from but that Product name may or may not contain phrase Wacom. Chris -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
Dnia 2012-02-11, sob o godzinie 03:27 +1000, Peter Hutterer pisze: > On Fri, Feb 10, 2012 at 04:56:11PM +, Przemo Firszt wrote: > > I was trying to find out why "xsetwacom --list devices" shows nothing > > and I found that my tablet is being handled by evdev. > > Details here: http://pastebin.com/jASCqiKC > > > > I can't see any "blacklisted devices" list in evdev, so I could exclude > > it nor I can see anything wrong in xorg driver for wacom (it's the same > > as for Graphire4 Bluetooth and for that one xsetwacom worked). > > > > Any ideas where to look for solution? > > /usr/share/X11/xorg.conf/d/50-wacom.conf on my machine matches mainly > against "Wacom" in the product name - that's missing on this device. Try > using MatchVendor, provided that contains a string that's matchable. > If so, pls let us know so we can update the .conf file. > Hi Peter, Spot on, 10/10, bull's-eye and the main prize :-) > [przemo@pldmachine ~]$ head /usr/share/X11/xorg.conf.d/50-wacom.conf > Section "InputClass" > Identifier "Wacom class" > MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection > > Section "InputClass" > Identifier "Wacom serial class" > MatchProduct "Serial Wacom Tablet" I added PTK-540WL to MatchProduct. I'm not sure if that's the best way, but it's hard to decide without knowing how other wacom devices are called. Patch on the way in a next 5 minutes. Thanks!! :-) -- Przemo -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
On Fri, Feb 10, 2012 at 04:56:11PM +, Przemo Firszt wrote: > I was trying to find out why "xsetwacom --list devices" shows nothing > and I found that my tablet is being handled by evdev. > Details here: http://pastebin.com/jASCqiKC > > I can't see any "blacklisted devices" list in evdev, so I could exclude > it nor I can see anything wrong in xorg driver for wacom (it's the same > as for Graphire4 Bluetooth and for that one xsetwacom worked). > > Any ideas where to look for solution? /usr/share/X11/xorg.conf/d/50-wacom.conf on my machine matches mainly against "Wacom" in the product name - that's missing on this device. Try using MatchVendor, provided that contains a string that's matchable. If so, pls let us know so we can update the .conf file. 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
[Linuxwacom-devel] Intuos4 WL is handled by evdev - what's wrong?
I was trying to find out why "xsetwacom --list devices" shows nothing and I found that my tablet is being handled by evdev. Details here: http://pastebin.com/jASCqiKC I can't see any "blacklisted devices" list in evdev, so I could exclude it nor I can see anything wrong in xorg driver for wacom (it's the same as for Graphire4 Bluetooth and for that one xsetwacom worked). Any ideas where to look for solution? -- Regards Przemo -- 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
