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] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
On Fri, Feb 10, 2012 at 02:00:13PM -0600, Chris Bagwell wrote: > On Fri, Feb 10, 2012 at 1:11 PM, Przemo Firszt 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 > >> wrote: > >> > On Fri, Feb 10, 2012 at 05:55:16PM +, 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 > >> > > >> > 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/pci:00/: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/pci:00/: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:056A:00BD > > 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:b0005v056Ap00BD > > 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 Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
Re: [Linuxwacom-devel] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
On Fri, Feb 10, 2012 at 1:11 PM, Przemo Firszt 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 >> wrote: >> > On Fri, Feb 10, 2012 at 05:55:16PM +, 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 >> > >> > 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/pci:00/: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/pci:00/: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:056A:00BD > 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:b0005v056Ap00BD > 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. 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] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
Dnia 2012-02-10, pią o godzinie 12:44 -0600, Chris Bagwell pisze: > On Fri, Feb 10, 2012 at 12:27 PM, Peter Hutterer > wrote: > > On Fri, Feb 10, 2012 at 05:55:16PM +, 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 > > > > 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: P: /devices/pci:00/: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/pci:00/: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:056A:00BD 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:b0005v056Ap00BD 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? -- 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] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
On Fri, Feb 10, 2012 at 12:27 PM, Peter Hutterer wrote: > On Fri, Feb 10, 2012 at 05:55:16PM +, 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 > > 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. Chris > > Cheers, > Peter > >> --- >> conf/50-wacom.conf | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/conf/50-wacom.conf b/conf/50-wacom.conf >> index 2c9ccb6..5cf5fdf 100644 >> --- a/conf/50-wacom.conf >> +++ b/conf/50-wacom.conf >> @@ -1,6 +1,6 @@ >> Section "InputClass" >> Identifier "Wacom class" >> - MatchProduct "Wacom|WACOM|WALTOP|Hanwang" >> + MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" >> MatchDevicePath "/dev/input/event*" >> Driver "wacom" >> EndSection >> -- >> 1.7.6.4 >> > > -- > 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 -- 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] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
On Fri, Feb 10, 2012 at 05:55:16PM +, 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 out of interest - did MatchVendor work at all? Cheers, Peter > --- > conf/50-wacom.conf |2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/conf/50-wacom.conf b/conf/50-wacom.conf > index 2c9ccb6..5cf5fdf 100644 > --- a/conf/50-wacom.conf > +++ b/conf/50-wacom.conf > @@ -1,6 +1,6 @@ > Section "InputClass" > Identifier "Wacom class" > - MatchProduct "Wacom|WACOM|WALTOP|Hanwang" > + MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" > MatchDevicePath "/dev/input/event*" > Driver "wacom" > EndSection > -- > 1.7.6.4 > -- 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] [PATCH] Add Wacom Intuos4 Wireless to 50-wacom.conf
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 --- conf/50-wacom.conf |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/conf/50-wacom.conf b/conf/50-wacom.conf index 2c9ccb6..5cf5fdf 100644 --- a/conf/50-wacom.conf +++ b/conf/50-wacom.conf @@ -1,6 +1,6 @@ Section "InputClass" Identifier "Wacom class" - MatchProduct "Wacom|WACOM|WALTOP|Hanwang" + MatchProduct "Wacom|WACOM|WALTOP|Hanwang|PTK-540WL" MatchDevicePath "/dev/input/event*" Driver "wacom" EndSection -- 1.7.6.4 -- 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
Re: [Linuxwacom-devel] [PATCH v3] Enable LED status change through xsetwacom
On Sat, Feb 11, 2012 at 12:03:19AM +0800, Ping Cheng wrote: > On Fri, Feb 10, 2012 at 4:29 PM, Peter Hutterer > wrote: > > > On Wed, Feb 08, 2012 at 08:30:58AM -0800, Jason Gerecke wrote: > > > On Wed, Jan 25, 2012 at 1:57 PM, Jason Gerecke > > wrote: > > > > This covers most of the suggested changes. I'm not sure yet how we > > > > want to expose the properties through X, so changes regarding that > > > > haven't been folded in. > > > > [...] > > > > > > Any feedback on the changes or ideas on exposing the properties? > > > > sorry for the delay. short answer - I don't think we should merge this > > support as properties. properties are not well-suited for this, they are > > too > > generic and too much knowledge must reside in the client setting them. > > > > Instead, we should extend the protocol for XI 2.3 > > > How do we support XI older than 2.3, then? we don't, at least not in xf86-input-wacom and I very much doubt that e.g. gnome would then. While I understand the need for keeping backwards-compat with older servers for new hardware, I don't think LED support is that crucial that we should merge and support an interface that can only be badly supported (and is driver-specific, again, like too many other features). If the need is that big, you could branch off but I doubt LED support is worth the effort. Cheers, Peter > > to add a LED class and the > > required requests to modify the LEDs support. This gives us > > more flexibility handling LEDs and less driver-dependent behaviour. > > > > 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
Re: [Linuxwacom-devel] [PATCH v3] Enable LED status change through xsetwacom
On Fri, Feb 10, 2012 at 4:29 PM, Peter Hutterer wrote: > On Wed, Feb 08, 2012 at 08:30:58AM -0800, Jason Gerecke wrote: > > On Wed, Jan 25, 2012 at 1:57 PM, Jason Gerecke > wrote: > > > This covers most of the suggested changes. I'm not sure yet how we > > > want to expose the properties through X, so changes regarding that > > > haven't been folded in. > > [...] > > > > Any feedback on the changes or ideas on exposing the properties? > > sorry for the delay. short answer - I don't think we should merge this > support as properties. properties are not well-suited for this, they are > too > generic and too much knowledge must reside in the client setting them. > > Instead, we should extend the protocol for XI 2.3 How do we support XI older than 2.3, then? Ping > to add a LED class and the > required requests to modify the LEDs support. This gives us > more flexibility handling LEDs and less driver-dependent behaviour. > > 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 > -- 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] [PATCH v3] Enable LED status change through xsetwacom
On Wed, Feb 08, 2012 at 08:30:58AM -0800, Jason Gerecke wrote: > On Wed, Jan 25, 2012 at 1:57 PM, Jason Gerecke wrote: > > This covers most of the suggested changes. I'm not sure yet how we > > want to expose the properties through X, so changes regarding that > > haven't been folded in. [...] > > Any feedback on the changes or ideas on exposing the properties? sorry for the delay. short answer - I don't think we should merge this support as properties. properties are not well-suited for this, they are too generic and too much knowledge must reside in the client setting them. Instead, we should extend the protocol for XI 2.3 to add a LED class and the required requests to modify the LEDs support. This gives us more flexibility handling LEDs and less driver-dependent behaviour. 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] [PATCH] Remove AC_CORE status print
On Thu, Feb 09, 2012 at 12:57:04PM -0800, Jason Gerecke wrote:
> Flag is deprecated, has no effect, and serves no purpose anymore.
> Remove from the DBG statement.
>
> Signed-off-by: Jason Gerecke
> ---
> src/wcmCommon.c |5 ++---
> 1 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/src/wcmCommon.c b/src/wcmCommon.c
> index 11340ea..034a3a3 100644
> --- a/src/wcmCommon.c
> +++ b/src/wcmCommon.c
> @@ -294,10 +294,9 @@ static void sendAButton(InputInfoPtr pInfo, int button,
> int mask,
> mapped_button = priv->button[button];
>
> DBG(4, priv, "TPCButton(%s) button=%d state=%d "
> - "mapped_button=%d, coreEvent=%s \n",
> + "mapped_button=%d\n",
> common->wcmTPCButton ? "on" : "off",
> - button, mask, mapped_button,
> - (mapped_button & AC_CORE) ? "yes" : "no");
> + button, mask, mapped_button);
>
> if (!priv->keys[mapped_button][0])
> {
> --
> 1.7.8.4
Reviewed-by: Peter Hutterer
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] [PATCH] Check for appropriate number of properties when setting buttons
On Thu, Feb 09, 2012 at 11:24:11AM -0800, Jason Gerecke wrote:
> Commit 7e92aca6 changed the length of the Wacom Button Actions
> property to be dynamically calculated, but did not take this
> into account for the property setter (preventing xsetwacom from
> updating them). This patch replaces the constant length with an
> identical calculation to ensure we check for the proper size.
>
> Signed-off-by: Jason Gerecke
> ---
> src/wcmXCommand.c |3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/src/wcmXCommand.c b/src/wcmXCommand.c
> index d0963f1..0fd5664 100644
> --- a/src/wcmXCommand.c
> +++ b/src/wcmXCommand.c
> @@ -849,7 +849,8 @@ int wcmSetProperty(DeviceIntPtr dev, Atom property,
> XIPropertyValuePtr prop,
> #endif
> } else if (property == prop_btnactions)
> {
> - if (prop->size != WCM_MAX_BUTTONS)
> + int nbuttons = min(max(priv->nbuttons + 4, 7), WCM_MAX_BUTTONS);
> + if (prop->size != nbuttons)
> return BadMatch;
> wcmSetPropertyButtonActions(dev, property, prop, checkonly);
> } else
> --
> 1.7.8.4
oops, sorry. Reviewed-by: Peter Hutterer
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] [PATCH] Remove redundant redeclaration of 'wcmInitialScreens'
On Thu, Feb 09, 2012 at 11:23:41AM -0800, Jason Gerecke wrote: > >From GCC: >In file included from ../src/xf86Wacom.c:46:0: >../src/xf86Wacom.h:147:13: warning: redundant redeclaration of >'wcmInitialScreens' [-Wredundant-decls] >../src/xf86Wacom.h:146:13: note: previous declaration of >'wcmInitialScreens' was here > > Signed-off-by: Jason Gerecke Reviewed-by: Peter Hutterer Cheers, Peter > --- > src/xf86Wacom.h |1 - > 1 files changed, 0 insertions(+), 1 deletions(-) > > diff --git a/src/xf86Wacom.h b/src/xf86Wacom.h > index fc1b4f4..ad45529 100644 > --- a/src/xf86Wacom.h > +++ b/src/xf86Wacom.h > @@ -144,7 +144,6 @@ extern Bool wcmPostInitParseOptions(InputInfoPtr pInfo, > Bool is_primary, Bool is > extern int wcmParseSerials(InputInfoPtr pinfo); > extern void wcmInitialCoordinates(InputInfoPtr pInfo, int axes); > extern void wcmInitialScreens(InputInfoPtr pInfo); > -extern void wcmInitialScreens(InputInfoPtr pInfo); > > extern int wcmDevSwitchModeCall(InputInfoPtr pInfo, int mode); > extern int wcmDevSwitchMode(ClientPtr client, DeviceIntPtr dev, int mode); > -- > 1.7.8.4 -- 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
