Re: [Linuxwacom-devel] Protocol for Intuos4 WL?
Dnia 2012-02-23, czw o godzinie 21:14 -0600, Chris Bagwell pisze: > On Wed, Feb 22, 2012 at 1:55 PM, Przemo Firszt wrote: > > I'm trying to track down a probem with Intuos4 WL. Connected by USB > > works OK: > > [ 3182.316] (II) /dev/input/event8 (10:wcmEvent): c=0 i=1050626 t=1c > > s=343955190 x=18061 y=9959 b=0 p=0 rz=0 tx=28 ty=32 aw=0 aw2=0 rw=0 t=0 > > px=1 st=0 cs=4 > > > > so serial is 343955190 (hex 148056F6), > > id 1050626 (hex 100802) or hex 10080A depending on the tool. > > > > now hid-wacom: > > > > [ 22269.565] (II) /dev/input/event8 (10:wcmEvent): c=0 i=0 t=1 s=1 > > x=32822 y=11354 b=0 p=0 rz=0 tx=0 ty=0 aw=0 aw2=0 rw=0 t=0 px=1 st=0 cs=4 > > > > so serial = 1, id =0 > > Based on later emails, looks like you have it under control but in > case your interested, here is some more info. > > I believe that xf86-input-wacom will support serial #'s if you declare > MSC_SERIAL in the probe() area of driver. xf86-input-wacom doesn't do > much more then pass it around; even for "generic" tablets. You could > make this change by itself. > > 'id' on the other hand comes from ABS_MISC. Yes, declaring that in > probe() will get it working but it also enables protocol 5 support. > > There is a few subtle issues but based on current hid-wacom it boils > down to this: when you finally add pad button support be sure and use > BTN_0/1/2/etc and not BTN_RIGHT/LEFT/etc. Lets just say Protocol 5 > and buttons are handled odd. Thanks for the info! I'm trying to figure out now why pen buttons are dead for pen, but work for eraser! I blame xorg driver for that ;-) I'll move to pad as soon as I have that sorted out. > > > > P.S. How to set debug level for tablet before connecting? I what to debug > > connection process, but > > xsetwacom --set "Wacom Intuos4 WL pad" TabletDebugLevel 10 can't work if > > there is no tablet connected. > > I've not tried it but Peter made some updates so you can set the debug > options in your 50-wacom.conf file and the driver looks for it very > early on. Thanks again! I'll give it a try and report back. -- 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] Protocol for Intuos4 WL?
On Wed, Feb 22, 2012 at 1:55 PM, Przemo Firszt wrote: > I'm trying to track down a probem with Intuos4 WL. Connected by USB > works OK: > [ 3182.316] (II) /dev/input/event8 (10:wcmEvent): c=0 i=1050626 t=1c > s=343955190 x=18061 y=9959 b=0 p=0 rz=0 tx=28 ty=32 aw=0 aw2=0 rw=0 t=0 > px=1 st=0 cs=4 > > so serial is 343955190 (hex 148056F6), > id 1050626 (hex 100802) or hex 10080A depending on the tool. > > now hid-wacom: > > [ 22269.565] (II) /dev/input/event8 (10:wcmEvent): c=0 i=0 t=1 s=1 > x=32822 y=11354 b=0 p=0 rz=0 tx=0 ty=0 aw=0 aw2=0 rw=0 t=0 px=1 st=0 cs=4 > > so serial = 1, id =0 Based on later emails, looks like you have it under control but in case your interested, here is some more info. I believe that xf86-input-wacom will support serial #'s if you declare MSC_SERIAL in the probe() area of driver. xf86-input-wacom doesn't do much more then pass it around; even for "generic" tablets. You could make this change by itself. 'id' on the other hand comes from ABS_MISC. Yes, declaring that in probe() will get it working but it also enables protocol 5 support. There is a few subtle issues but based on current hid-wacom it boils down to this: when you finally add pad button support be sure and use BTN_0/1/2/etc and not BTN_RIGHT/LEFT/etc. Lets just say Protocol 5 and buttons are handled odd. > > P.S. How to set debug level for tablet before connecting? I what to debug > connection process, but > xsetwacom --set "Wacom Intuos4 WL pad" TabletDebugLevel 10 can't work if > there is no tablet connected. I've not tried it but Peter made some updates so you can set the debug options in your 50-wacom.conf file and the driver looks for it very early on. 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] Protocol for Intuos4 WL?
Dnia 2012-02-22, śro o godzinie 19:55 +, Przemo Firszt pisze: [..] > I understand that usbInitProtocol5 should initialise protocol v5 but I can't > find where it's called. > The same for usbInitProtocol4. > > Any hints? > I'll answer my own question: absbit wasn't set in kernel driver. Adding __set_bit(ABS_MISC, input->absbit); solved the problem. -- 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
[Linuxwacom-devel] Protocol for Intuos4 WL?
I'm trying to track down a probem with Intuos4 WL. Connected by USB works OK: [ 3182.316] (II) /dev/input/event8 (10:wcmEvent): c=0 i=1050626 t=1c s=343955190 x=18061 y=9959 b=0 p=0 rz=0 tx=28 ty=32 aw=0 aw2=0 rw=0 t=0 px=1 st=0 cs=4 so serial is 343955190 (hex 148056F6), id 1050626 (hex 100802) or hex 10080A depending on the tool. now hid-wacom: [ 22269.565] (II) /dev/input/event8 (10:wcmEvent): c=0 i=0 t=1 s=1 x=32822 y=11354 b=0 p=0 rz=0 tx=0 ty=0 aw=0 aw2=0 rw=0 t=0 px=1 st=0 cs=4 so serial = 1, id =0 part of the code related to reporting: input_report_key(input, BTN_TOUCH, pressure > 1); input_report_abs(input, ABS_DISTANCE, ((data[9] >> 3) & 0x3f)); input_report_key(input, BTN_STYLUS, data[1] & 0x02); input_report_key(input, BTN_STYLUS2, data[1] & 0x04); input_report_abs(input, ABS_X, x); input_report_abs(input, ABS_Y, y); input_report_abs(input, ABS_PRESSURE, pressure); input_report_abs(input, ABS_MISC, wdata->id); input_report_key(input, wdata->tool, 1); input_event(input, EV_MSC, MSC_SERIAL, wdata->serial); input_sync(input); values on kernel side are correct, I can prove it :-) My guess is that usbChooseChannel is picking WCM_PROTOCOL_GENERIC I understand that usbInitProtocol5 should initialise protocol v5 but I can't find where it's called. The same for usbInitProtocol4. Any hints? P.S. How to set debug level for tablet before connecting? I what to debug connection process, but xsetwacom --set "Wacom Intuos4 WL pad" TabletDebugLevel 10 can't work if there is no tablet connected. -- regards Przemo Firszt -- 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
