Bamboo Pad

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Bamboo Pad

thermatk(EZN)
Hello!
Got it working by making it initialized by hid driver (just as Chris Wallace in this mailing list before) but using xorg.conf files also got the touchpad working, the pressure support of the tablet and understood that "keyboard" input device is not fake but a strange way Bamboo Pad gives us three-finger swipes. It's all the same for USB (0x0318) and Wireless (0x0319) versions.
Can someone please help me make this support beautiful, mainlined and full(without quirks all over the place), now that it's known to work?
My steps now are:
1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline
2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad and keyboard parts to "evdev" drivers, while tablet remains under the reign of "wacom" from 50-wacom.conf
I have tried to add ids to hid-wacom in kernel and got nothing, just as Chris Wallace.
My proposal:
1. Add the device id to the kernel hid driver to the devices with special configuration returing "false" in hid_ignore function in drivers/hid/hid-core.c
Should I send such a patch to Linux kernel somewhere?
It's working, here is what I did:

@@ -2488,6 +2488,11 @@
strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
return true;
break;
+ case USB_VENDOR_ID_WACOM:
+ if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
+ hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
+ return false;
+ break;
}
if (hdev->type == HID_TYPE_USBMOUSE &&
Of course, there are also the ids added to the header file.

2. Add device support to xf86-input-wacom, it already works good, just needs to know about it all the details and support it out-of-the-box
Sincerely,
Ruslan Boitsov

--
Go digital

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Bamboo Pad

Jason Gerecke
Things are a in flux at the moment with the kernel driver. The goal is
to have the Wacom driver live under the HID subsystem and benefit from
automatically supporting devices with useful data in their HID
descriptors. The just-released Linux 3.17 kernel how has the driver
living HID, but we're still working on introducing the necessary
flexibility to make the second half of our goal a reality.

It would be interesting to know how your tablet works with what is
being worked on upstream. Could you clone the following repository,
and try using your tablet with the "for-3.18/wacom" branch? I've have
trouble getting touch to work with that branch (so you might not have
any luck with the Bamboo Pad...) but it would be good to know if it
creates all the necessary input devices or not.

git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git

Also, would it be possible for you to attach the device's HID
descriptor and lsusb output? The binary descriptor should be located
at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
the '????' bit being the USB interface number), while you can run
`sudo lsusb -v -d 056a:0319` to get the later.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]> wrote:

> Hello!
> Got it working by making it initialized by hid driver (just as Chris Wallace
> in this mailing list before) but using xorg.conf files also got the touchpad
> working, the pressure support of the tablet and understood that "keyboard"
> input device is not fake but a strange way Bamboo Pad gives us three-finger
> swipes. It's all the same for USB (0x0318) and Wireless (0x0319) versions.
> Can someone please help me make this support beautiful, mainlined and
> full(without quirks all over the place), now that it's known to work?
> My steps now are:
> 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline
> 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad and
> keyboard parts to "evdev" drivers, while tablet remains under the reign of
> "wacom" from 50-wacom.conf
> I have tried to add ids to hid-wacom in kernel and got nothing, just as
> Chris Wallace.
> My proposal:
> 1. Add the device id to the kernel hid driver to the devices with special
> configuration returing "false" in hid_ignore function in
> drivers/hid/hid-core.c
> Should I send such a patch to Linux kernel somewhere?
> It's working, here is what I did:
>
> @@ -2488,6 +2488,11 @@
>   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>   return true;
>   break;
> + case USB_VENDOR_ID_WACOM:
> + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
> +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
> + return false;
> + break;
>   }
>   if (hdev->type == HID_TYPE_USBMOUSE &&
>
> Of course, there are also the ids added to the header file.
>
> 2. Add device support to xf86-input-wacom, it already works good, just needs
> to know about it all the details and support it out-of-the-box
> Sincerely,
> Ruslan Boitsov
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

------------------------------------------------------------------------------
Slashdot TV.  Videos for Nerds.  Stuff that Matters.
http://pubads.g.doubleclick.net/gampad/clk?id=160591471&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Bamboo Pad

thermatk(EZN)
[Mailing list asked me to reduce the size of the message, resending]
So, descriptors and output from terminal are attached. With this kernel device is seen without quirks, but not working at all. wacom driver is unloaded, evdev loaded manually doesn't work for now, evtest shows no reaction to input. Hope you understand what's going wrong here

2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
Things are a in flux at the moment with the kernel driver. The goal is
to have the Wacom driver live under the HID subsystem and benefit from
automatically supporting devices with useful data in their HID
descriptors. The just-released Linux 3.17 kernel how has the driver
living HID, but we're still working on introducing the necessary
flexibility to make the second half of our goal a reality.

It would be interesting to know how your tablet works with what is
being worked on upstream. Could you clone the following repository,
and try using your tablet with the "for-3.18/wacom" branch? I've have
trouble getting touch to work with that branch (so you might not have
any luck with the Bamboo Pad...) but it would be good to know if it
creates all the necessary input devices or not.

git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git

Also, would it be possible for you to attach the device's HID
descriptor and lsusb output? The binary descriptor should be located
at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
the '????' bit being the USB interface number), while you can run
`sudo lsusb -v -d 056a:0319` to get the later.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]> wrote:
> Hello!
> Got it working by making it initialized by hid driver (just as Chris Wallace
> in this mailing list before) but using xorg.conf files also got the touchpad
> working, the pressure support of the tablet and understood that "keyboard"
> input device is not fake but a strange way Bamboo Pad gives us three-finger
> swipes. It's all the same for USB (0x0318) and Wireless (0x0319) versions.
> Can someone please help me make this support beautiful, mainlined and
> full(without quirks all over the place), now that it's known to work?
> My steps now are:
> 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline
> 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad and
> keyboard parts to "evdev" drivers, while tablet remains under the reign of
> "wacom" from 50-wacom.conf
> I have tried to add ids to hid-wacom in kernel and got nothing, just as
> Chris Wallace.
> My proposal:
> 1. Add the device id to the kernel hid driver to the devices with special
> configuration returing "false" in hid_ignore function in
> drivers/hid/hid-core.c
> Should I send such a patch to Linux kernel somewhere?
> It's working, here is what I did:
>
> @@ -2488,6 +2488,11 @@
>   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>   return true;
>   break;
> + case USB_VENDOR_ID_WACOM:
> + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
> +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
> + return false;
> + break;
>   }
>   if (hdev->type == HID_TYPE_USBMOUSE &&
>
> Of course, there are also the ids added to the header file.
>
> 2. Add device support to xf86-input-wacom, it already works good, just needs
> to know about it all the details and support it out-of-the-box
> Sincerely,
> Ruslan Boitsov
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>



--
Go digital

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss

terminal.txt (18K) Download Attachment
000B.desc (134 bytes) Download Attachment
000C.desc (176 bytes) Download Attachment
000D.desc (60 bytes) Download Attachment
000E.desc (72 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Bamboo Pad

Jason Gerecke
Thanks :) I was hoping the pen interface might work since you had luck
getting HID core to recognize it, but I'm not terribly surprised that
it doesn't. There's still a number of things that could be tripping up
and causing the kernel driver to mishandle autoconfiguration in its
current state.

Could you attach the header output from evtest? It looks like the X
driver does not detect any of the devices as a pen, which is odd for a
different reason. I wonder what events are being advertised by the
kernel device to userland...

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]> wrote:

> [Mailing list asked me to reduce the size of the message, resending]
> So, descriptors and output from terminal are attached. With this kernel
> device is seen without quirks, but not working at all. wacom driver is
> unloaded, evdev loaded manually doesn't work for now, evtest shows no
> reaction to input. Hope you understand what's going wrong here
>
> 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Things are a in flux at the moment with the kernel driver. The goal is
>> to have the Wacom driver live under the HID subsystem and benefit from
>> automatically supporting devices with useful data in their HID
>> descriptors. The just-released Linux 3.17 kernel how has the driver
>> living HID, but we're still working on introducing the necessary
>> flexibility to make the second half of our goal a reality.
>>
>> It would be interesting to know how your tablet works with what is
>> being worked on upstream. Could you clone the following repository,
>> and try using your tablet with the "for-3.18/wacom" branch? I've have
>> trouble getting touch to work with that branch (so you might not have
>> any luck with the Bamboo Pad...) but it would be good to know if it
>> creates all the necessary input devices or not.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>>
>> Also, would it be possible for you to attach the device's HID
>> descriptor and lsusb output? The binary descriptor should be located
>> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> the '????' bit being the USB interface number), while you can run
>> `sudo lsusb -v -d 056a:0319` to get the later.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> > Hello!
>> > Got it working by making it initialized by hid driver (just as Chris
>> > Wallace
>> > in this mailing list before) but using xorg.conf files also got the
>> > touchpad
>> > working, the pressure support of the tablet and understood that
>> > "keyboard"
>> > input device is not fake but a strange way Bamboo Pad gives us
>> > three-finger
>> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> > versions.
>> > Can someone please help me make this support beautiful, mainlined and
>> > full(without quirks all over the place), now that it's known to work?
>> > My steps now are:
>> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline
>> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad and
>> > keyboard parts to "evdev" drivers, while tablet remains under the reign
>> > of
>> > "wacom" from 50-wacom.conf
>> > I have tried to add ids to hid-wacom in kernel and got nothing, just as
>> > Chris Wallace.
>> > My proposal:
>> > 1. Add the device id to the kernel hid driver to the devices with
>> > special
>> > configuration returing "false" in hid_ignore function in
>> > drivers/hid/hid-core.c
>> > Should I send such a patch to Linux kernel somewhere?
>> > It's working, here is what I did:
>> >
>> > @@ -2488,6 +2488,11 @@
>> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >   return true;
>> >   break;
>> > + case USB_VENDOR_ID_WACOM:
>> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> > + return false;
>> > + break;
>> >   }
>> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >
>> > Of course, there are also the ids added to the header file.
>> >
>> > 2. Add device support to xf86-input-wacom, it already works good, just
>> > needs
>> > to know about it all the details and support it out-of-the-box
>> > Sincerely,
>> > Ruslan Boitsov
>> >
>> > --
>> > Go digital
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Linuxwacom-discuss mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >
>
>
>
>
> --
> Go digital

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Fwd: Bamboo Pad

thermatk(EZN)

---------- Forwarded message ----------
From: thermatk(EZN) <[hidden email]>
Date: 2014-10-07 21:28 GMT+04:00
Subject: Re: [Linuxwacom-discuss] Bamboo Pad
To: Jason Gerecke <[hidden email]>


They all show the same:
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x56a product 0x319 version 0x110
Input device name: "Wacom HID Pen"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
  Event type 3 (EV_ABS)
Properties:
Testing ... (interrupt to exit)

And nothing happens if I touch with fingers or pen in any of the 4 event devices:
/dev/input/event23:    Wacom HID Pen
/dev/input/event24:    Wacom HID Pen
/dev/input/event25:    Wacom HID Pen
/dev/input/event26:    Wacom HID Pen

With hid-core there were three devices - a tablet(stylus&eraser together?), a touchpad with 2 fingers support and a keyboard which was sending three-finger swipes as keyboard events(Super+D, Alt+Left, etc)


2014-10-07 20:55 GMT+04:00 Jason Gerecke <[hidden email]>:
Thanks :) I was hoping the pen interface might work since you had luck
getting HID core to recognize it, but I'm not terribly surprised that
it doesn't. There's still a number of things that could be tripping up
and causing the kernel driver to mishandle autoconfiguration in its
current state.

Could you attach the header output from evtest? It looks like the X
driver does not detect any of the devices as a pen, which is odd for a
different reason. I wonder what events are being advertised by the
kernel device to userland...

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]> wrote:
> [Mailing list asked me to reduce the size of the message, resending]
> So, descriptors and output from terminal are attached. With this kernel
> device is seen without quirks, but not working at all. wacom driver is
> unloaded, evdev loaded manually doesn't work for now, evtest shows no
> reaction to input. Hope you understand what's going wrong here
>
> 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Things are a in flux at the moment with the kernel driver. The goal is
>> to have the Wacom driver live under the HID subsystem and benefit from
>> automatically supporting devices with useful data in their HID
>> descriptors. The just-released Linux 3.17 kernel how has the driver
>> living HID, but we're still working on introducing the necessary
>> flexibility to make the second half of our goal a reality.
>>
>> It would be interesting to know how your tablet works with what is
>> being worked on upstream. Could you clone the following repository,
>> and try using your tablet with the "for-3.18/wacom" branch? I've have
>> trouble getting touch to work with that branch (so you might not have
>> any luck with the Bamboo Pad...) but it would be good to know if it
>> creates all the necessary input devices or not.
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>>
>> Also, would it be possible for you to attach the device's HID
>> descriptor and lsusb output? The binary descriptor should be located
>> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> the '????' bit being the USB interface number), while you can run
>> `sudo lsusb -v -d 056a:0319` to get the later.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> > Hello!
>> > Got it working by making it initialized by hid driver (just as Chris
>> > Wallace
>> > in this mailing list before) but using xorg.conf files also got the
>> > touchpad
>> > working, the pressure support of the tablet and understood that
>> > "keyboard"
>> > input device is not fake but a strange way Bamboo Pad gives us
>> > three-finger
>> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> > versions.
>> > Can someone please help me make this support beautiful, mainlined and
>> > full(without quirks all over the place), now that it's known to work?
>> > My steps now are:
>> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot cmdline
>> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad and
>> > keyboard parts to "evdev" drivers, while tablet remains under the reign
>> > of
>> > "wacom" from 50-wacom.conf
>> > I have tried to add ids to hid-wacom in kernel and got nothing, just as
>> > Chris Wallace.
>> > My proposal:
>> > 1. Add the device id to the kernel hid driver to the devices with
>> > special
>> > configuration returing "false" in hid_ignore function in
>> > drivers/hid/hid-core.c
>> > Should I send such a patch to Linux kernel somewhere?
>> > It's working, here is what I did:
>> >
>> > @@ -2488,6 +2488,11 @@
>> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >   return true;
>> >   break;
>> > + case USB_VENDOR_ID_WACOM:
>> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> > + return false;
>> > + break;
>> >   }
>> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >
>> > Of course, there are also the ids added to the header file.
>> >
>> > 2. Add device support to xf86-input-wacom, it already works good, just
>> > needs
>> > to know about it all the details and support it out-of-the-box
>> > Sincerely,
>> > Ruslan Boitsov
>> >
>> > --
>> > Go digital
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Linuxwacom-discuss mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >
>
>
>
>
> --
> Go digital



--
Go digital



--
Go digital

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Bamboo Pad

Jason Gerecke
Very interesting. It almost looks like the driver is ignoring the
descriptors, but I'm not sure why that'd happen. The patches were
designed with tablet PCs in mind, but I don't remember seeing anything
that would have been incompatible with other tablets with useful data
in their HID descriptors.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Oct 7, 2014 at 10:44 AM, thermatk(EZN) <[hidden email]> wrote:

>
> ---------- Forwarded message ----------
> From: thermatk(EZN) <[hidden email]>
> Date: 2014-10-07 21:28 GMT+04:00
> Subject: Re: [Linuxwacom-discuss] Bamboo Pad
> To: Jason Gerecke <[hidden email]>
>
>
> They all show the same:
> Input driver version is 1.0.1
> Input device ID: bus 0x3 vendor 0x56a product 0x319 version 0x110
> Input device name: "Wacom HID Pen"
> Supported events:
>   Event type 0 (EV_SYN)
>   Event type 1 (EV_KEY)
>   Event type 3 (EV_ABS)
> Properties:
> Testing ... (interrupt to exit)
>
> And nothing happens if I touch with fingers or pen in any of the 4 event
> devices:
> /dev/input/event23:    Wacom HID Pen
> /dev/input/event24:    Wacom HID Pen
> /dev/input/event25:    Wacom HID Pen
> /dev/input/event26:    Wacom HID Pen
>
> With hid-core there were three devices - a tablet(stylus&eraser together?),
> a touchpad with 2 fingers support and a keyboard which was sending
> three-finger swipes as keyboard events(Super+D, Alt+Left, etc)
>
>
> 2014-10-07 20:55 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Thanks :) I was hoping the pen interface might work since you had luck
>> getting HID core to recognize it, but I'm not terribly surprised that
>> it doesn't. There's still a number of things that could be tripping up
>> and causing the kernel driver to mishandle autoconfiguration in its
>> current state.
>>
>> Could you attach the header output from evtest? It looks like the X
>> driver does not detect any of the devices as a pen, which is odd for a
>> different reason. I wonder what events are being advertised by the
>> kernel device to userland...
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> > [Mailing list asked me to reduce the size of the message, resending]
>> > So, descriptors and output from terminal are attached. With this kernel
>> > device is seen without quirks, but not working at all. wacom driver is
>> > unloaded, evdev loaded manually doesn't work for now, evtest shows no
>> > reaction to input. Hope you understand what's going wrong here
>> >
>> > 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >>
>> >> Things are a in flux at the moment with the kernel driver. The goal is
>> >> to have the Wacom driver live under the HID subsystem and benefit from
>> >> automatically supporting devices with useful data in their HID
>> >> descriptors. The just-released Linux 3.17 kernel how has the driver
>> >> living HID, but we're still working on introducing the necessary
>> >> flexibility to make the second half of our goal a reality.
>> >>
>> >> It would be interesting to know how your tablet works with what is
>> >> being worked on upstream. Could you clone the following repository,
>> >> and try using your tablet with the "for-3.18/wacom" branch? I've have
>> >> trouble getting touch to work with that branch (so you might not have
>> >> any luck with the Bamboo Pad...) but it would be good to know if it
>> >> creates all the necessary input devices or not.
>> >>
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>> >>
>> >> Also, would it be possible for you to attach the device's HID
>> >> descriptor and lsusb output? The binary descriptor should be located
>> >> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> >> the '????' bit being the USB interface number), while you can run
>> >> `sudo lsusb -v -d 056a:0319` to get the later.
>> >>
>> >> Jason
>> >> ---
>> >> Now instead of four in the eights place /
>> >> you’ve got three, ‘Cause you added one  /
>> >> (That is to say, eight) to the two,     /
>> >> But you can’t take seven from three,    /
>> >> So you look at the sixty-fours....
>> >>
>> >>
>> >>
>> >> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> >> wrote:
>> >> > Hello!
>> >> > Got it working by making it initialized by hid driver (just as Chris
>> >> > Wallace
>> >> > in this mailing list before) but using xorg.conf files also got the
>> >> > touchpad
>> >> > working, the pressure support of the tablet and understood that
>> >> > "keyboard"
>> >> > input device is not fake but a strange way Bamboo Pad gives us
>> >> > three-finger
>> >> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> >> > versions.
>> >> > Can someone please help me make this support beautiful, mainlined and
>> >> > full(without quirks all over the place), now that it's known to work?
>> >> > My steps now are:
>> >> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot
>> >> > cmdline
>> >> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad
>> >> > and
>> >> > keyboard parts to "evdev" drivers, while tablet remains under the
>> >> > reign
>> >> > of
>> >> > "wacom" from 50-wacom.conf
>> >> > I have tried to add ids to hid-wacom in kernel and got nothing, just
>> >> > as
>> >> > Chris Wallace.
>> >> > My proposal:
>> >> > 1. Add the device id to the kernel hid driver to the devices with
>> >> > special
>> >> > configuration returing "false" in hid_ignore function in
>> >> > drivers/hid/hid-core.c
>> >> > Should I send such a patch to Linux kernel somewhere?
>> >> > It's working, here is what I did:
>> >> >
>> >> > @@ -2488,6 +2488,11 @@
>> >> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >> >   return true;
>> >> >   break;
>> >> > + case USB_VENDOR_ID_WACOM:
>> >> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> >> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> >> > + return false;
>> >> > + break;
>> >> >   }
>> >> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >> >
>> >> > Of course, there are also the ids added to the header file.
>> >> >
>> >> > 2. Add device support to xf86-input-wacom, it already works good,
>> >> > just
>> >> > needs
>> >> > to know about it all the details and support it out-of-the-box
>> >> > Sincerely,
>> >> > Ruslan Boitsov
>> >> >
>> >> > --
>> >> > Go digital
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> > Reports
>> >> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> >> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >> >
>> >> >
>> >> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> > _______________________________________________
>> >> > Linuxwacom-discuss mailing list
>> >> > [hidden email]
>> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Go digital
>
>
>
>
> --
> Go digital
>
>
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Bamboo Pad

thermatk(EZN)
Is it the moment where I should use a kernel with a lot of printk() here and there? If it is, I don't know where to put them. I have only found using code-search that hid-waltop driver overrides some of the descriptors for their tablets with fixed ones. Yet the descriptors in BambooPad were all right when using hid-core, I don't know what I say and what it means really :)


2014-10-07 22:02 GMT+04:00 Jason Gerecke <[hidden email]>:
Very interesting. It almost looks like the driver is ignoring the
descriptors, but I'm not sure why that'd happen. The patches were
designed with tablet PCs in mind, but I don't remember seeing anything
that would have been incompatible with other tablets with useful data
in their HID descriptors.

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....



On Tue, Oct 7, 2014 at 10:44 AM, thermatk(EZN) <[hidden email]> wrote:
>
> ---------- Forwarded message ----------
> From: thermatk(EZN) <[hidden email]>
> Date: 2014-10-07 21:28 GMT+04:00
> Subject: Re: [Linuxwacom-discuss] Bamboo Pad
> To: Jason Gerecke <[hidden email]>
>
>
> They all show the same:
> Input driver version is 1.0.1
> Input device ID: bus 0x3 vendor 0x56a product 0x319 version 0x110
> Input device name: "Wacom HID Pen"
> Supported events:
>   Event type 0 (EV_SYN)
>   Event type 1 (EV_KEY)
>   Event type 3 (EV_ABS)
> Properties:
> Testing ... (interrupt to exit)
>
> And nothing happens if I touch with fingers or pen in any of the 4 event
> devices:
> /dev/input/event23:    Wacom HID Pen
> /dev/input/event24:    Wacom HID Pen
> /dev/input/event25:    Wacom HID Pen
> /dev/input/event26:    Wacom HID Pen
>
> With hid-core there were three devices - a tablet(stylus&eraser together?),
> a touchpad with 2 fingers support and a keyboard which was sending
> three-finger swipes as keyboard events(Super+D, Alt+Left, etc)
>
>
> 2014-10-07 20:55 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Thanks :) I was hoping the pen interface might work since you had luck
>> getting HID core to recognize it, but I'm not terribly surprised that
>> it doesn't. There's still a number of things that could be tripping up
>> and causing the kernel driver to mishandle autoconfiguration in its
>> current state.
>>
>> Could you attach the header output from evtest? It looks like the X
>> driver does not detect any of the devices as a pen, which is odd for a
>> different reason. I wonder what events are being advertised by the
>> kernel device to userland...
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> > [Mailing list asked me to reduce the size of the message, resending]
>> > So, descriptors and output from terminal are attached. With this kernel
>> > device is seen without quirks, but not working at all. wacom driver is
>> > unloaded, evdev loaded manually doesn't work for now, evtest shows no
>> > reaction to input. Hope you understand what's going wrong here
>> >
>> > 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >>
>> >> Things are a in flux at the moment with the kernel driver. The goal is
>> >> to have the Wacom driver live under the HID subsystem and benefit from
>> >> automatically supporting devices with useful data in their HID
>> >> descriptors. The just-released Linux 3.17 kernel how has the driver
>> >> living HID, but we're still working on introducing the necessary
>> >> flexibility to make the second half of our goal a reality.
>> >>
>> >> It would be interesting to know how your tablet works with what is
>> >> being worked on upstream. Could you clone the following repository,
>> >> and try using your tablet with the "for-3.18/wacom" branch? I've have
>> >> trouble getting touch to work with that branch (so you might not have
>> >> any luck with the Bamboo Pad...) but it would be good to know if it
>> >> creates all the necessary input devices or not.
>> >>
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>> >>
>> >> Also, would it be possible for you to attach the device's HID
>> >> descriptor and lsusb output? The binary descriptor should be located
>> >> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> >> the '????' bit being the USB interface number), while you can run
>> >> `sudo lsusb -v -d 056a:0319` to get the later.
>> >>
>> >> Jason
>> >> ---
>> >> Now instead of four in the eights place /
>> >> you’ve got three, ‘Cause you added one  /
>> >> (That is to say, eight) to the two,     /
>> >> But you can’t take seven from three,    /
>> >> So you look at the sixty-fours....
>> >>
>> >>
>> >>
>> >> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> >> wrote:
>> >> > Hello!
>> >> > Got it working by making it initialized by hid driver (just as Chris
>> >> > Wallace
>> >> > in this mailing list before) but using xorg.conf files also got the
>> >> > touchpad
>> >> > working, the pressure support of the tablet and understood that
>> >> > "keyboard"
>> >> > input device is not fake but a strange way Bamboo Pad gives us
>> >> > three-finger
>> >> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> >> > versions.
>> >> > Can someone please help me make this support beautiful, mainlined and
>> >> > full(without quirks all over the place), now that it's known to work?
>> >> > My steps now are:
>> >> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot
>> >> > cmdline
>> >> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the touchpad
>> >> > and
>> >> > keyboard parts to "evdev" drivers, while tablet remains under the
>> >> > reign
>> >> > of
>> >> > "wacom" from 50-wacom.conf
>> >> > I have tried to add ids to hid-wacom in kernel and got nothing, just
>> >> > as
>> >> > Chris Wallace.
>> >> > My proposal:
>> >> > 1. Add the device id to the kernel hid driver to the devices with
>> >> > special
>> >> > configuration returing "false" in hid_ignore function in
>> >> > drivers/hid/hid-core.c
>> >> > Should I send such a patch to Linux kernel somewhere?
>> >> > It's working, here is what I did:
>> >> >
>> >> > @@ -2488,6 +2488,11 @@
>> >> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >> >   return true;
>> >> >   break;
>> >> > + case USB_VENDOR_ID_WACOM:
>> >> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> >> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> >> > + return false;
>> >> > + break;
>> >> >   }
>> >> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >> >
>> >> > Of course, there are also the ids added to the header file.
>> >> >
>> >> > 2. Add device support to xf86-input-wacom, it already works good,
>> >> > just
>> >> > needs
>> >> > to know about it all the details and support it out-of-the-box
>> >> > Sincerely,
>> >> > Ruslan Boitsov
>> >> >
>> >> > --
>> >> > Go digital
>> >> >
>> >> >
>> >> >
>> >> > ------------------------------------------------------------------------------
>> >> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> > Reports
>> >> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> >> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >> >
>> >> >
>> >> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> > _______________________________________________
>> >> > Linuxwacom-discuss mailing list
>> >> > [hidden email]
>> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >> >
>> >
>> >
>> >
>> >
>> > --
>> > Go digital
>
>
>
>
> --
> Go digital
>
>
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>



--
Go digital

------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Bamboo Pad

Andrea Arteaga
Dear thermatk, Jason and everybody else,
I have a Bamboo Pad Wireless and I'm willing to participate to the
testing, if not the development, of the driver. I am a very
experienced linux user, but I have no experience with writing kernel
modules and hardware.

I'm currently under fedora21 with the kernel 3.17. I am really willing
to mess it up for the sake of testing the tablet :-)

Can I do something for helping you? i will need in any case some
information about linuxwacom: How it works and how to work with it.
Where can I find it?

All the best
Andrea

2014-10-08 6:59 GMT+02:00 thermatk(EZN) <[hidden email]>:

> Is it the moment where I should use a kernel with a lot of printk() here and
> there? If it is, I don't know where to put them. I have only found using
> code-search that hid-waltop driver overrides some of the descriptors for
> their tablets with fixed ones. Yet the descriptors in BambooPad were all
> right when using hid-core, I don't know what I say and what it means really
> :)
>
>
> 2014-10-07 22:02 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Very interesting. It almost looks like the driver is ignoring the
>> descriptors, but I'm not sure why that'd happen. The patches were
>> designed with tablet PCs in mind, but I don't remember seeing anything
>> that would have been incompatible with other tablets with useful data
>> in their HID descriptors.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Tue, Oct 7, 2014 at 10:44 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> >
>> > ---------- Forwarded message ----------
>> > From: thermatk(EZN) <[hidden email]>
>> > Date: 2014-10-07 21:28 GMT+04:00
>> > Subject: Re: [Linuxwacom-discuss] Bamboo Pad
>> > To: Jason Gerecke <[hidden email]>
>> >
>> >
>> > They all show the same:
>> > Input driver version is 1.0.1
>> > Input device ID: bus 0x3 vendor 0x56a product 0x319 version 0x110
>> > Input device name: "Wacom HID Pen"
>> > Supported events:
>> >   Event type 0 (EV_SYN)
>> >   Event type 1 (EV_KEY)
>> >   Event type 3 (EV_ABS)
>> > Properties:
>> > Testing ... (interrupt to exit)
>> >
>> > And nothing happens if I touch with fingers or pen in any of the 4 event
>> > devices:
>> > /dev/input/event23:    Wacom HID Pen
>> > /dev/input/event24:    Wacom HID Pen
>> > /dev/input/event25:    Wacom HID Pen
>> > /dev/input/event26:    Wacom HID Pen
>> >
>> > With hid-core there were three devices - a tablet(stylus&eraser
>> > together?),
>> > a touchpad with 2 fingers support and a keyboard which was sending
>> > three-finger swipes as keyboard events(Super+D, Alt+Left, etc)
>> >
>> >
>> > 2014-10-07 20:55 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >>
>> >> Thanks :) I was hoping the pen interface might work since you had luck
>> >> getting HID core to recognize it, but I'm not terribly surprised that
>> >> it doesn't. There's still a number of things that could be tripping up
>> >> and causing the kernel driver to mishandle autoconfiguration in its
>> >> current state.
>> >>
>> >> Could you attach the header output from evtest? It looks like the X
>> >> driver does not detect any of the devices as a pen, which is odd for a
>> >> different reason. I wonder what events are being advertised by the
>> >> kernel device to userland...
>> >>
>> >> Jason
>> >> ---
>> >> Now instead of four in the eights place /
>> >> you’ve got three, ‘Cause you added one  /
>> >> (That is to say, eight) to the two,     /
>> >> But you can’t take seven from three,    /
>> >> So you look at the sixty-fours....
>> >>
>> >>
>> >>
>> >> On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> >> wrote:
>> >> > [Mailing list asked me to reduce the size of the message, resending]
>> >> > So, descriptors and output from terminal are attached. With this
>> >> > kernel
>> >> > device is seen without quirks, but not working at all. wacom driver
>> >> > is
>> >> > unloaded, evdev loaded manually doesn't work for now, evtest shows no
>> >> > reaction to input. Hope you understand what's going wrong here
>> >> >
>> >> > 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >> >>
>> >> >> Things are a in flux at the moment with the kernel driver. The goal
>> >> >> is
>> >> >> to have the Wacom driver live under the HID subsystem and benefit
>> >> >> from
>> >> >> automatically supporting devices with useful data in their HID
>> >> >> descriptors. The just-released Linux 3.17 kernel how has the driver
>> >> >> living HID, but we're still working on introducing the necessary
>> >> >> flexibility to make the second half of our goal a reality.
>> >> >>
>> >> >> It would be interesting to know how your tablet works with what is
>> >> >> being worked on upstream. Could you clone the following repository,
>> >> >> and try using your tablet with the "for-3.18/wacom" branch? I've
>> >> >> have
>> >> >> trouble getting touch to work with that branch (so you might not
>> >> >> have
>> >> >> any luck with the Bamboo Pad...) but it would be good to know if it
>> >> >> creates all the necessary input devices or not.
>> >> >>
>> >> >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>> >> >>
>> >> >> Also, would it be possible for you to attach the device's HID
>> >> >> descriptor and lsusb output? The binary descriptor should be located
>> >> >> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> >> >> the '????' bit being the USB interface number), while you can run
>> >> >> `sudo lsusb -v -d 056a:0319` to get the later.
>> >> >>
>> >> >> Jason
>> >> >> ---
>> >> >> Now instead of four in the eights place /
>> >> >> you’ve got three, ‘Cause you added one  /
>> >> >> (That is to say, eight) to the two,     /
>> >> >> But you can’t take seven from three,    /
>> >> >> So you look at the sixty-fours....
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN)
>> >> >> <[hidden email]>
>> >> >> wrote:
>> >> >> > Hello!
>> >> >> > Got it working by making it initialized by hid driver (just as
>> >> >> > Chris
>> >> >> > Wallace
>> >> >> > in this mailing list before) but using xorg.conf files also got
>> >> >> > the
>> >> >> > touchpad
>> >> >> > working, the pressure support of the tablet and understood that
>> >> >> > "keyboard"
>> >> >> > input device is not fake but a strange way Bamboo Pad gives us
>> >> >> > three-finger
>> >> >> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> >> >> > versions.
>> >> >> > Can someone please help me make this support beautiful, mainlined
>> >> >> > and
>> >> >> > full(without quirks all over the place), now that it's known to
>> >> >> > work?
>> >> >> > My steps now are:
>> >> >> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot
>> >> >> > cmdline
>> >> >> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the
>> >> >> > touchpad
>> >> >> > and
>> >> >> > keyboard parts to "evdev" drivers, while tablet remains under the
>> >> >> > reign
>> >> >> > of
>> >> >> > "wacom" from 50-wacom.conf
>> >> >> > I have tried to add ids to hid-wacom in kernel and got nothing,
>> >> >> > just
>> >> >> > as
>> >> >> > Chris Wallace.
>> >> >> > My proposal:
>> >> >> > 1. Add the device id to the kernel hid driver to the devices with
>> >> >> > special
>> >> >> > configuration returing "false" in hid_ignore function in
>> >> >> > drivers/hid/hid-core.c
>> >> >> > Should I send such a patch to Linux kernel somewhere?
>> >> >> > It's working, here is what I did:
>> >> >> >
>> >> >> > @@ -2488,6 +2488,11 @@
>> >> >> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >> >> >   return true;
>> >> >> >   break;
>> >> >> > + case USB_VENDOR_ID_WACOM:
>> >> >> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> >> >> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> >> >> > + return false;
>> >> >> > + break;
>> >> >> >   }
>> >> >> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >> >> >
>> >> >> > Of course, there are also the ids added to the header file.
>> >> >> >
>> >> >> > 2. Add device support to xf86-input-wacom, it already works good,
>> >> >> > just
>> >> >> > needs
>> >> >> > to know about it all the details and support it out-of-the-box
>> >> >> > Sincerely,
>> >> >> > Ruslan Boitsov
>> >> >> >
>> >> >> > --
>> >> >> > Go digital
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > ------------------------------------------------------------------------------
>> >> >> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> >> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> >> > Reports
>> >> >> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White
>> >> >> > paper
>> >> >> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
>> >> >> > Analyzer
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> >> > _______________________________________________
>> >> >> > Linuxwacom-discuss mailing list
>> >> >> > [hidden email]
>> >> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Go digital
>> >
>> >
>> >
>> >
>> > --
>> > Go digital
>> >
>> >
>> >
>> > --
>> > Go digital
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Linuxwacom-discuss mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >
>
>
>
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
Reply | Threaded
Open this post in threaded view
|

Re: Fwd: Bamboo Pad

thermatk(EZN)

Hi Andrea!
To get the thing working with 3.17 you can use my workaround from first message but what happens after the 3.18 patch which is totally rewriting wacom and hid is a question for someone else and now I couldn't even think of a workaround. I'm not a kernel developer too and can't understand why it's not working as intended.
Sincerely

20 окт. 2014 г. 2:48 пользователь "Andrea Arteaga" <[hidden email]> написал:
Dear thermatk, Jason and everybody else,
I have a Bamboo Pad Wireless and I'm willing to participate to the
testing, if not the development, of the driver. I am a very
experienced linux user, but I have no experience with writing kernel
modules and hardware.

I'm currently under fedora21 with the kernel 3.17. I am really willing
to mess it up for the sake of testing the tablet :-)

Can I do something for helping you? i will need in any case some
information about linuxwacom: How it works and how to work with it.
Where can I find it?

All the best
Andrea

2014-10-08 6:59 GMT+02:00 thermatk(EZN) <[hidden email]>:
> Is it the moment where I should use a kernel with a lot of printk() here and
> there? If it is, I don't know where to put them. I have only found using
> code-search that hid-waltop driver overrides some of the descriptors for
> their tablets with fixed ones. Yet the descriptors in BambooPad were all
> right when using hid-core, I don't know what I say and what it means really
> :)
>
>
> 2014-10-07 22:02 GMT+04:00 Jason Gerecke <[hidden email]>:
>>
>> Very interesting. It almost looks like the driver is ignoring the
>> descriptors, but I'm not sure why that'd happen. The patches were
>> designed with tablet PCs in mind, but I don't remember seeing anything
>> that would have been incompatible with other tablets with useful data
>> in their HID descriptors.
>>
>> Jason
>> ---
>> Now instead of four in the eights place /
>> you’ve got three, ‘Cause you added one  /
>> (That is to say, eight) to the two,     /
>> But you can’t take seven from three,    /
>> So you look at the sixty-fours....
>>
>>
>>
>> On Tue, Oct 7, 2014 at 10:44 AM, thermatk(EZN) <[hidden email]>
>> wrote:
>> >
>> > ---------- Forwarded message ----------
>> > From: thermatk(EZN) <[hidden email]>
>> > Date: 2014-10-07 21:28 GMT+04:00
>> > Subject: Re: [Linuxwacom-discuss] Bamboo Pad
>> > To: Jason Gerecke <[hidden email]>
>> >
>> >
>> > They all show the same:
>> > Input driver version is 1.0.1
>> > Input device ID: bus 0x3 vendor 0x56a product 0x319 version 0x110
>> > Input device name: "Wacom HID Pen"
>> > Supported events:
>> >   Event type 0 (EV_SYN)
>> >   Event type 1 (EV_KEY)
>> >   Event type 3 (EV_ABS)
>> > Properties:
>> > Testing ... (interrupt to exit)
>> >
>> > And nothing happens if I touch with fingers or pen in any of the 4 event
>> > devices:
>> > /dev/input/event23:    Wacom HID Pen
>> > /dev/input/event24:    Wacom HID Pen
>> > /dev/input/event25:    Wacom HID Pen
>> > /dev/input/event26:    Wacom HID Pen
>> >
>> > With hid-core there were three devices - a tablet(stylus&eraser
>> > together?),
>> > a touchpad with 2 fingers support and a keyboard which was sending
>> > three-finger swipes as keyboard events(Super+D, Alt+Left, etc)
>> >
>> >
>> > 2014-10-07 20:55 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >>
>> >> Thanks :) I was hoping the pen interface might work since you had luck
>> >> getting HID core to recognize it, but I'm not terribly surprised that
>> >> it doesn't. There's still a number of things that could be tripping up
>> >> and causing the kernel driver to mishandle autoconfiguration in its
>> >> current state.
>> >>
>> >> Could you attach the header output from evtest? It looks like the X
>> >> driver does not detect any of the devices as a pen, which is odd for a
>> >> different reason. I wonder what events are being advertised by the
>> >> kernel device to userland...
>> >>
>> >> Jason
>> >> ---
>> >> Now instead of four in the eights place /
>> >> you’ve got three, ‘Cause you added one  /
>> >> (That is to say, eight) to the two,     /
>> >> But you can’t take seven from three,    /
>> >> So you look at the sixty-fours....
>> >>
>> >>
>> >>
>> >> On Tue, Oct 7, 2014 at 3:27 AM, thermatk(EZN) <[hidden email]>
>> >> wrote:
>> >> > [Mailing list asked me to reduce the size of the message, resending]
>> >> > So, descriptors and output from terminal are attached. With this
>> >> > kernel
>> >> > device is seen without quirks, but not working at all. wacom driver
>> >> > is
>> >> > unloaded, evdev loaded manually doesn't work for now, evtest shows no
>> >> > reaction to input. Hope you understand what's going wrong here
>> >> >
>> >> > 2014-10-07 0:32 GMT+04:00 Jason Gerecke <[hidden email]>:
>> >> >>
>> >> >> Things are a in flux at the moment with the kernel driver. The goal
>> >> >> is
>> >> >> to have the Wacom driver live under the HID subsystem and benefit
>> >> >> from
>> >> >> automatically supporting devices with useful data in their HID
>> >> >> descriptors. The just-released Linux 3.17 kernel how has the driver
>> >> >> living HID, but we're still working on introducing the necessary
>> >> >> flexibility to make the second half of our goal a reality.
>> >> >>
>> >> >> It would be interesting to know how your tablet works with what is
>> >> >> being worked on upstream. Could you clone the following repository,
>> >> >> and try using your tablet with the "for-3.18/wacom" branch? I've
>> >> >> have
>> >> >> trouble getting touch to work with that branch (so you might not
>> >> >> have
>> >> >> any luck with the Bamboo Pad...) but it would be good to know if it
>> >> >> creates all the necessary input devices or not.
>> >> >>
>> >> >> git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
>> >> >>
>> >> >> Also, would it be possible for you to attach the device's HID
>> >> >> descriptor and lsusb output? The binary descriptor should be located
>> >> >> at /sys/bus/hid/devices/0003:056A:0319.????/report_descriptor (with
>> >> >> the '????' bit being the USB interface number), while you can run
>> >> >> `sudo lsusb -v -d 056a:0319` to get the later.
>> >> >>
>> >> >> Jason
>> >> >> ---
>> >> >> Now instead of four in the eights place /
>> >> >> you’ve got three, ‘Cause you added one  /
>> >> >> (That is to say, eight) to the two,     /
>> >> >> But you can’t take seven from three,    /
>> >> >> So you look at the sixty-fours....
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Sat, Oct 4, 2014 at 3:27 AM, thermatk(EZN)
>> >> >> <[hidden email]>
>> >> >> wrote:
>> >> >> > Hello!
>> >> >> > Got it working by making it initialized by hid driver (just as
>> >> >> > Chris
>> >> >> > Wallace
>> >> >> > in this mailing list before) but using xorg.conf files also got
>> >> >> > the
>> >> >> > touchpad
>> >> >> > working, the pressure support of the tablet and understood that
>> >> >> > "keyboard"
>> >> >> > input device is not fake but a strange way Bamboo Pad gives us
>> >> >> > three-finger
>> >> >> > swipes. It's all the same for USB (0x0318) and Wireless (0x0319)
>> >> >> > versions.
>> >> >> > Can someone please help me make this support beautiful, mainlined
>> >> >> > and
>> >> >> > full(without quirks all over the place), now that it's known to
>> >> >> > work?
>> >> >> > My steps now are:
>> >> >> > 1. Add usbhid.quirks=0x056a:0x0319:0x40000000 to the grub boot
>> >> >> > cmdline
>> >> >> > 2. With a custom 51-bamboopad.conf in xorg.conf.d match the
>> >> >> > touchpad
>> >> >> > and
>> >> >> > keyboard parts to "evdev" drivers, while tablet remains under the
>> >> >> > reign
>> >> >> > of
>> >> >> > "wacom" from 50-wacom.conf
>> >> >> > I have tried to add ids to hid-wacom in kernel and got nothing,
>> >> >> > just
>> >> >> > as
>> >> >> > Chris Wallace.
>> >> >> > My proposal:
>> >> >> > 1. Add the device id to the kernel hid driver to the devices with
>> >> >> > special
>> >> >> > configuration returing "false" in hid_ignore function in
>> >> >> > drivers/hid/hid-core.c
>> >> >> > Should I send such a patch to Linux kernel somewhere?
>> >> >> > It's working, here is what I did:
>> >> >> >
>> >> >> > @@ -2488,6 +2488,11 @@
>> >> >> >   strncmp(hdev->name, "www.masterkit.ru MA901", 22) == 0)
>> >> >> >   return true;
>> >> >> >   break;
>> >> >> > + case USB_VENDOR_ID_WACOM:
>> >> >> > + if (hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_USB ||
>> >> >> > +    hdev->product == USB_DEVICE_ID_WACOM_BAMBOOPAD_WIRELESS)
>> >> >> > + return false;
>> >> >> > + break;
>> >> >> >   }
>> >> >> >   if (hdev->type == HID_TYPE_USBMOUSE &&
>> >> >> >
>> >> >> > Of course, there are also the ids added to the header file.
>> >> >> >
>> >> >> > 2. Add device support to xf86-input-wacom, it already works good,
>> >> >> > just
>> >> >> > needs
>> >> >> > to know about it all the details and support it out-of-the-box
>> >> >> > Sincerely,
>> >> >> > Ruslan Boitsov
>> >> >> >
>> >> >> > --
>> >> >> > Go digital
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > ------------------------------------------------------------------------------
>> >> >> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> >> >> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS
>> >> >> > Reports
>> >> >> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White
>> >> >> > paper
>> >> >> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
>> >> >> > Analyzer
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> >> >> > _______________________________________________
>> >> >> > Linuxwacom-discuss mailing list
>> >> >> > [hidden email]
>> >> >> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >> >> >
>> >> >
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Go digital
>> >
>> >
>> >
>> >
>> > --
>> > Go digital
>> >
>> >
>> >
>> > --
>> > Go digital
>> >
>> >
>> > ------------------------------------------------------------------------------
>> > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
>> > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
>> > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
>> > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>> >
>> > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>> > _______________________________________________
>> > Linuxwacom-discuss mailing list
>> > [hidden email]
>> > https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>> >
>
>
>
>
> --
> Go digital
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Linuxwacom-discuss mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss
>

------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Linuxwacom-discuss mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-discuss