digimend-users Mailing List for DIGImend (Page 20)
Brought to you by:
spb_nick
You can subscribe to this list here.
2012 |
Jan
|
Feb
|
Mar
|
Apr
(58) |
May
(72) |
Jun
(24) |
Jul
|
Aug
(12) |
Sep
(9) |
Oct
(10) |
Nov
(2) |
Dec
(4) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2013 |
Jan
(5) |
Feb
(23) |
Mar
|
Apr
|
May
(4) |
Jun
(7) |
Jul
(2) |
Aug
(2) |
Sep
(5) |
Oct
(7) |
Nov
(31) |
Dec
(11) |
2014 |
Jan
(13) |
Feb
(4) |
Mar
(1) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
(12) |
Aug
(10) |
Sep
(13) |
Oct
(15) |
Nov
(49) |
Dec
(4) |
2015 |
Jan
(49) |
Feb
(62) |
Mar
(81) |
Apr
(10) |
May
(4) |
Jun
(6) |
Jul
(17) |
Aug
(3) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
(8) |
2016 |
Jan
(8) |
Feb
(5) |
Mar
(7) |
Apr
(7) |
May
(3) |
Jun
(4) |
Jul
(12) |
Aug
(8) |
Sep
(6) |
Oct
(4) |
Nov
(1) |
Dec
|
From: Nikolai K. <sp...@gm...> - 2012-05-15 12:54:59
|
Hi Zauber, On 05/15/2012 04:41 AM, Zauber Paracelsus wrote: > Since it may be a bit before the bug is fixed on Xorg's end, I'm > thinking of trying an alternative solution, but I'd like to know if and > how it would work: > > 1) Create some kind of "fake" monitor/screen > 2) Configure the files in /etc/X11/xorg.conf.d/ so that the tablet will > only give its input to this fake screen > 3) Access the fake screen through VNC. > > How viable would this solution be? Or would it be better to hook the > tablet up to my laptop and use VNC to use programs on my desktop > through the laptop? > > PS: Just using it directly with my laptop isn't viable, as my laptop > isn't powerful enough to directly handle the complex drawings I want to > make, while my desktop is more than enough. Sorry, I don't know if this would work. However, some time ago Peter Hutterer made a patch for the Git version of the X server and attached it to the reported bug: https://bugs.freedesktop.org/show_bug.cgi?id=49347 I'm having a flu and didn't have the time to test it properly yet. However, it should apply to your version, it seems, so you could try it yourself. I've managed to backport this patch to 1.11.4 (attached) and test it - it seems to work. Sincerely, Nick |
From: Jiri K. <jk...@su...> - 2012-05-15 07:54:29
|
On Mon, 14 May 2012, Nikolai Kondrashov wrote: > Add support for UC-Logic Wireless Tablet TWHL850. > It is known to be sold as Genius MousePen M508W. > > This tablet has a bug in the default (compatibility) mode which is used in this > driver: frame button assignments are mixed up. This is to be fixed with a driver > using proprietary protocol, which is to be fully reverse-engineered yet. > > Signed-off-by: Nikolai Kondrashov <sp...@gm...> > --- > > This version has IFACE_RDESC_FIXUP macro expanded as requested by Jiri. > > drivers/hid/hid-core.c | 1 + > drivers/hid/hid-ids.h | 1 + > drivers/hid/hid-uclogic.c | 141 +++++++++++++++++++++++++++++++++++++++++++++ > 3 files changed, 143 insertions(+) > > diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c > index 4da66b4..c25fc49 100644 > --- a/drivers/hid/hid-core.c > +++ b/drivers/hid/hid-core.c > @@ -1562,6 +1562,7 @@ static const struct hid_device_id hid_have_special_driver[] = { > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP5540U) }, > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U) }, > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP1062) }, > + { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850) }, > { HID_USB_DEVICE(USB_VENDOR_ID_UNITEC, USB_DEVICE_ID_UNITEC_USB_TOUCH_0709) }, > { HID_USB_DEVICE(USB_VENDOR_ID_UNITEC, USB_DEVICE_ID_UNITEC_USB_TOUCH_0A19) }, > { HID_USB_DEVICE(USB_VENDOR_ID_WISEGROUP, USB_DEVICE_ID_SMARTJOY_PLUS) }, > diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h > index e39aecb..ad8d743 100644 > --- a/drivers/hid/hid-ids.h > +++ b/drivers/hid/hid-ids.h > @@ -726,6 +726,7 @@ > #define USB_DEVICE_ID_UCLOGIC_TABLET_WP5540U 0x0004 > #define USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U 0x0005 > #define USB_DEVICE_ID_UCLOGIC_TABLET_WP1062 0x0064 > +#define USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850 0x0522 > > #define USB_VENDOR_ID_UNITEC 0x227d > #define USB_DEVICE_ID_UNITEC_USB_TOUCH_0709 0x0709 > diff --git a/drivers/hid/hid-uclogic.c b/drivers/hid/hid-uclogic.c > index 1f11289..3aba02b 100644 > --- a/drivers/hid/hid-uclogic.c > +++ b/drivers/hid/hid-uclogic.c > @@ -14,6 +14,7 @@ > #include <linux/device.h> > #include <linux/hid.h> > #include <linux/module.h> > +#include <linux/usb.h> > > #include "hid-ids.h" > > @@ -352,9 +353,125 @@ static __u8 pf1209_rdesc_fixed[] = { > 0xC0 /* End Collection */ > }; > > +/* > + * See TWHL850 description, device and HID report descriptors at > + * http://sf.net/apps/mediawiki/digimend/?title=UC-Logic_Wireless_Tablet_TWHL850 > + */ > + > +/* Size of the original descriptors of TWHL850 tablet */ > +#define TWHL850_RDESC_ORIG_SIZE0 182 > +#define TWHL850_RDESC_ORIG_SIZE1 161 > +#define TWHL850_RDESC_ORIG_SIZE2 92 > + > +/* Fixed PID 0522 tablet report descriptor, interface 0 (stylus) */ > +static __u8 twhl850_rdesc_fixed0[] = { > + 0x05, 0x0D, /* Usage Page (Digitizer), */ > + 0x09, 0x02, /* Usage (Pen), */ > + 0xA1, 0x01, /* Collection (Application), */ > + 0x85, 0x09, /* Report ID (9), */ > + 0x09, 0x20, /* Usage (Stylus), */ > + 0xA0, /* Collection (Physical), */ > + 0x14, /* Logical Minimum (0), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x75, 0x01, /* Report Size (1), */ > + 0x95, 0x03, /* Report Count (3), */ > + 0x09, 0x42, /* Usage (Tip Switch), */ > + 0x09, 0x44, /* Usage (Barrel Switch), */ > + 0x09, 0x46, /* Usage (Tablet Pick), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x81, 0x03, /* Input (Constant, Variable), */ > + 0x95, 0x01, /* Report Count (1), */ > + 0x09, 0x32, /* Usage (In Range), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x81, 0x03, /* Input (Constant, Variable), */ > + 0x75, 0x10, /* Report Size (16), */ > + 0xA4, /* Push, */ > + 0x05, 0x01, /* Usage Page (Desktop), */ > + 0x65, 0x13, /* Unit (Inch), */ > + 0x55, 0xFD, /* Unit Exponent (-3), */ > + 0x34, /* Physical Minimum (0), */ > + 0x09, 0x30, /* Usage (X), */ > + 0x46, 0x40, 0x1F, /* Physical Maximum (8000), */ > + 0x26, 0x00, 0x7D, /* Logical Maximum (32000), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x09, 0x31, /* Usage (Y), */ > + 0x46, 0x88, 0x13, /* Physical Maximum (5000), */ > + 0x26, 0x20, 0x4E, /* Logical Maximum (20000), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0xB4, /* Pop, */ > + 0x09, 0x30, /* Usage (Tip Pressure), */ > + 0x26, 0xFF, 0x03, /* Logical Maximum (1023), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0xC0, /* End Collection, */ > + 0xC0 /* End Collection */ > +}; > + > +/* Fixed PID 0522 tablet report descriptor, interface 1 (mouse) */ > +static __u8 twhl850_rdesc_fixed1[] = { > + 0x05, 0x01, /* Usage Page (Desktop), */ > + 0x09, 0x02, /* Usage (Mouse), */ > + 0xA1, 0x01, /* Collection (Application), */ > + 0x85, 0x01, /* Report ID (1), */ > + 0x09, 0x01, /* Usage (Pointer), */ > + 0xA0, /* Collection (Physical), */ > + 0x05, 0x09, /* Usage Page (Button), */ > + 0x75, 0x01, /* Report Size (1), */ > + 0x95, 0x03, /* Report Count (3), */ > + 0x19, 0x01, /* Usage Minimum (01h), */ > + 0x29, 0x03, /* Usage Maximum (03h), */ > + 0x14, /* Logical Minimum (0), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x95, 0x05, /* Report Count (5), */ > + 0x81, 0x03, /* Input (Constant, Variable), */ > + 0x05, 0x01, /* Usage Page (Desktop), */ > + 0x09, 0x30, /* Usage (X), */ > + 0x09, 0x31, /* Usage (Y), */ > + 0x16, 0x00, 0x80, /* Logical Minimum (-32768), */ > + 0x26, 0xFF, 0x7F, /* Logical Maximum (32767), */ > + 0x75, 0x10, /* Report Size (16), */ > + 0x95, 0x02, /* Report Count (2), */ > + 0x81, 0x06, /* Input (Variable, Relative), */ > + 0x09, 0x38, /* Usage (Wheel), */ > + 0x15, 0xFF, /* Logical Minimum (-1), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x95, 0x01, /* Report Count (1), */ > + 0x75, 0x08, /* Report Size (8), */ > + 0x81, 0x06, /* Input (Variable, Relative), */ > + 0x81, 0x03, /* Input (Constant, Variable), */ > + 0xC0, /* End Collection, */ > + 0xC0 /* End Collection */ > +}; > + > +/* Fixed PID 0522 tablet report descriptor, interface 2 (frame buttons) */ > +static __u8 twhl850_rdesc_fixed2[] = { > + 0x05, 0x01, /* Usage Page (Desktop), */ > + 0x09, 0x06, /* Usage (Keyboard), */ > + 0xA1, 0x01, /* Collection (Application), */ > + 0x85, 0x03, /* Report ID (3), */ > + 0x05, 0x07, /* Usage Page (Keyboard), */ > + 0x14, /* Logical Minimum (0), */ > + 0x19, 0xE0, /* Usage Minimum (KB Leftcontrol), */ > + 0x29, 0xE7, /* Usage Maximum (KB Right GUI), */ > + 0x25, 0x01, /* Logical Maximum (1), */ > + 0x75, 0x01, /* Report Size (1), */ > + 0x95, 0x08, /* Report Count (8), */ > + 0x81, 0x02, /* Input (Variable), */ > + 0x18, /* Usage Minimum (None), */ > + 0x29, 0xFF, /* Usage Maximum (FFh), */ > + 0x26, 0xFF, 0x00, /* Logical Maximum (255), */ > + 0x75, 0x08, /* Report Size (8), */ > + 0x95, 0x06, /* Report Count (6), */ > + 0x80, /* Input, */ > + 0xC0 /* End Collection */ > +}; > + > static __u8 *uclogic_report_fixup(struct hid_device *hdev, __u8 *rdesc, > unsigned int *rsize) > { > + struct usb_interface *iface = to_usb_interface(hdev->dev.parent); > + __u8 iface_num = iface->cur_altsetting->desc.bInterfaceNumber; > + > switch (hdev->product) { > case USB_DEVICE_ID_UCLOGIC_TABLET_PF1209: > if (*rsize == PF1209_RDESC_ORIG_SIZE) { > @@ -386,6 +503,28 @@ static __u8 *uclogic_report_fixup(struct hid_device *hdev, __u8 *rdesc, > *rsize = sizeof(wp1062_rdesc_fixed); > } > break; > + case USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850: > + switch (iface_num) { > + case 0: > + if (*rsize == TWHL850_RDESC_ORIG_SIZE0) { > + rdesc = twhl850_rdesc_fixed0; > + *rsize = sizeof(twhl850_rdesc_fixed0); > + } > + break; > + case 1: > + if (*rsize == TWHL850_RDESC_ORIG_SIZE1) { > + rdesc = twhl850_rdesc_fixed1; > + *rsize = sizeof(twhl850_rdesc_fixed1); > + } > + break; > + case 2: > + if (*rsize == TWHL850_RDESC_ORIG_SIZE2) { > + rdesc = twhl850_rdesc_fixed2; > + *rsize = sizeof(twhl850_rdesc_fixed2); > + } > + break; > + } > + break; > } > > return rdesc; > @@ -402,6 +541,8 @@ static const struct hid_device_id uclogic_devices[] = { > USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U) }, > { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, > USB_DEVICE_ID_UCLOGIC_TABLET_WP1062) }, > + { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, > + USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850) }, > { } > }; > MODULE_DEVICE_TABLE(hid, uclogic_devices); Applied. Thanks Nikolai. -- Jiri Kosina SUSE Labs |
From: Zauber P. <zau...@gm...> - 2012-05-15 01:41:58
|
Since it may be a bit before the bug is fixed on Xorg's end, I'm thinking of trying an alternative solution, but I'd like to know if and how it would work: 1) Create some kind of "fake" monitor/screen 2) Configure the files in /etc/X11/xorg.conf.d/ so that the tablet will only give its input to this fake screen 3) Access the fake screen through VNC. How viable would this solution be? Or would it be better to hook the tablet up to my laptop and use VNC to use programs on my desktop through the laptop? PS: Just using it directly with my laptop isn't viable, as my laptop isn't powerful enough to directly handle the complex drawings I want to make, while my desktop is more than enough. On Mon, 07 May 2012 11:11:06 +0300 Nikolai Kondrashov <sp...@gm...> wrote: > Hi Zauber, > > On 04/19/2012 11:51 PM, Zauber Paracelsus wrote: > > Alright, thanks for the update, Nick :-) > > I think, my first guess was right and X.org is really just > re-transforming the old values of missing axes. > > I've submitted an X.org bug: > https://bugs.freedesktop.org/show_bug.cgi?id=49347 as I'm failing to > find time to find a good fix for this, sorry. > > Hopefully, someone notices and fixes it in Git. Then we could > backport the fix to your X.org version. > > Sorry for the delay. > > Sincerely, > Nick |
From: Nikolai K. <sp...@gm...> - 2012-05-14 17:31:17
|
Add support for UC-Logic Wireless Tablet TWHL850. It is known to be sold as Genius MousePen M508W. This tablet has a bug in the default (compatibility) mode which is used in this driver: frame button assignments are mixed up. This is to be fixed with a driver using proprietary protocol, which is to be fully reverse-engineered yet. Signed-off-by: Nikolai Kondrashov <sp...@gm...> --- This version has IFACE_RDESC_FIXUP macro expanded as requested by Jiri. drivers/hid/hid-core.c | 1 + drivers/hid/hid-ids.h | 1 + drivers/hid/hid-uclogic.c | 141 +++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 143 insertions(+) diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c index 4da66b4..c25fc49 100644 --- a/drivers/hid/hid-core.c +++ b/drivers/hid/hid-core.c @@ -1562,6 +1562,7 @@ static const struct hid_device_id hid_have_special_driver[] = { { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP5540U) }, { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U) }, { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP1062) }, + { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850) }, { HID_USB_DEVICE(USB_VENDOR_ID_UNITEC, USB_DEVICE_ID_UNITEC_USB_TOUCH_0709) }, { HID_USB_DEVICE(USB_VENDOR_ID_UNITEC, USB_DEVICE_ID_UNITEC_USB_TOUCH_0A19) }, { HID_USB_DEVICE(USB_VENDOR_ID_WISEGROUP, USB_DEVICE_ID_SMARTJOY_PLUS) }, diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h index e39aecb..ad8d743 100644 --- a/drivers/hid/hid-ids.h +++ b/drivers/hid/hid-ids.h @@ -726,6 +726,7 @@ #define USB_DEVICE_ID_UCLOGIC_TABLET_WP5540U 0x0004 #define USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U 0x0005 #define USB_DEVICE_ID_UCLOGIC_TABLET_WP1062 0x0064 +#define USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850 0x0522 #define USB_VENDOR_ID_UNITEC 0x227d #define USB_DEVICE_ID_UNITEC_USB_TOUCH_0709 0x0709 diff --git a/drivers/hid/hid-uclogic.c b/drivers/hid/hid-uclogic.c index 1f11289..3aba02b 100644 --- a/drivers/hid/hid-uclogic.c +++ b/drivers/hid/hid-uclogic.c @@ -14,6 +14,7 @@ #include <linux/device.h> #include <linux/hid.h> #include <linux/module.h> +#include <linux/usb.h> #include "hid-ids.h" @@ -352,9 +353,125 @@ static __u8 pf1209_rdesc_fixed[] = { 0xC0 /* End Collection */ }; +/* + * See TWHL850 description, device and HID report descriptors at + * http://sf.net/apps/mediawiki/digimend/?title=UC-Logic_Wireless_Tablet_TWHL850 + */ + +/* Size of the original descriptors of TWHL850 tablet */ +#define TWHL850_RDESC_ORIG_SIZE0 182 +#define TWHL850_RDESC_ORIG_SIZE1 161 +#define TWHL850_RDESC_ORIG_SIZE2 92 + +/* Fixed PID 0522 tablet report descriptor, interface 0 (stylus) */ +static __u8 twhl850_rdesc_fixed0[] = { + 0x05, 0x0D, /* Usage Page (Digitizer), */ + 0x09, 0x02, /* Usage (Pen), */ + 0xA1, 0x01, /* Collection (Application), */ + 0x85, 0x09, /* Report ID (9), */ + 0x09, 0x20, /* Usage (Stylus), */ + 0xA0, /* Collection (Physical), */ + 0x14, /* Logical Minimum (0), */ + 0x25, 0x01, /* Logical Maximum (1), */ + 0x75, 0x01, /* Report Size (1), */ + 0x95, 0x03, /* Report Count (3), */ + 0x09, 0x42, /* Usage (Tip Switch), */ + 0x09, 0x44, /* Usage (Barrel Switch), */ + 0x09, 0x46, /* Usage (Tablet Pick), */ + 0x81, 0x02, /* Input (Variable), */ + 0x81, 0x03, /* Input (Constant, Variable), */ + 0x95, 0x01, /* Report Count (1), */ + 0x09, 0x32, /* Usage (In Range), */ + 0x81, 0x02, /* Input (Variable), */ + 0x81, 0x03, /* Input (Constant, Variable), */ + 0x75, 0x10, /* Report Size (16), */ + 0xA4, /* Push, */ + 0x05, 0x01, /* Usage Page (Desktop), */ + 0x65, 0x13, /* Unit (Inch), */ + 0x55, 0xFD, /* Unit Exponent (-3), */ + 0x34, /* Physical Minimum (0), */ + 0x09, 0x30, /* Usage (X), */ + 0x46, 0x40, 0x1F, /* Physical Maximum (8000), */ + 0x26, 0x00, 0x7D, /* Logical Maximum (32000), */ + 0x81, 0x02, /* Input (Variable), */ + 0x09, 0x31, /* Usage (Y), */ + 0x46, 0x88, 0x13, /* Physical Maximum (5000), */ + 0x26, 0x20, 0x4E, /* Logical Maximum (20000), */ + 0x81, 0x02, /* Input (Variable), */ + 0xB4, /* Pop, */ + 0x09, 0x30, /* Usage (Tip Pressure), */ + 0x26, 0xFF, 0x03, /* Logical Maximum (1023), */ + 0x81, 0x02, /* Input (Variable), */ + 0xC0, /* End Collection, */ + 0xC0 /* End Collection */ +}; + +/* Fixed PID 0522 tablet report descriptor, interface 1 (mouse) */ +static __u8 twhl850_rdesc_fixed1[] = { + 0x05, 0x01, /* Usage Page (Desktop), */ + 0x09, 0x02, /* Usage (Mouse), */ + 0xA1, 0x01, /* Collection (Application), */ + 0x85, 0x01, /* Report ID (1), */ + 0x09, 0x01, /* Usage (Pointer), */ + 0xA0, /* Collection (Physical), */ + 0x05, 0x09, /* Usage Page (Button), */ + 0x75, 0x01, /* Report Size (1), */ + 0x95, 0x03, /* Report Count (3), */ + 0x19, 0x01, /* Usage Minimum (01h), */ + 0x29, 0x03, /* Usage Maximum (03h), */ + 0x14, /* Logical Minimum (0), */ + 0x25, 0x01, /* Logical Maximum (1), */ + 0x81, 0x02, /* Input (Variable), */ + 0x95, 0x05, /* Report Count (5), */ + 0x81, 0x03, /* Input (Constant, Variable), */ + 0x05, 0x01, /* Usage Page (Desktop), */ + 0x09, 0x30, /* Usage (X), */ + 0x09, 0x31, /* Usage (Y), */ + 0x16, 0x00, 0x80, /* Logical Minimum (-32768), */ + 0x26, 0xFF, 0x7F, /* Logical Maximum (32767), */ + 0x75, 0x10, /* Report Size (16), */ + 0x95, 0x02, /* Report Count (2), */ + 0x81, 0x06, /* Input (Variable, Relative), */ + 0x09, 0x38, /* Usage (Wheel), */ + 0x15, 0xFF, /* Logical Minimum (-1), */ + 0x25, 0x01, /* Logical Maximum (1), */ + 0x95, 0x01, /* Report Count (1), */ + 0x75, 0x08, /* Report Size (8), */ + 0x81, 0x06, /* Input (Variable, Relative), */ + 0x81, 0x03, /* Input (Constant, Variable), */ + 0xC0, /* End Collection, */ + 0xC0 /* End Collection */ +}; + +/* Fixed PID 0522 tablet report descriptor, interface 2 (frame buttons) */ +static __u8 twhl850_rdesc_fixed2[] = { + 0x05, 0x01, /* Usage Page (Desktop), */ + 0x09, 0x06, /* Usage (Keyboard), */ + 0xA1, 0x01, /* Collection (Application), */ + 0x85, 0x03, /* Report ID (3), */ + 0x05, 0x07, /* Usage Page (Keyboard), */ + 0x14, /* Logical Minimum (0), */ + 0x19, 0xE0, /* Usage Minimum (KB Leftcontrol), */ + 0x29, 0xE7, /* Usage Maximum (KB Right GUI), */ + 0x25, 0x01, /* Logical Maximum (1), */ + 0x75, 0x01, /* Report Size (1), */ + 0x95, 0x08, /* Report Count (8), */ + 0x81, 0x02, /* Input (Variable), */ + 0x18, /* Usage Minimum (None), */ + 0x29, 0xFF, /* Usage Maximum (FFh), */ + 0x26, 0xFF, 0x00, /* Logical Maximum (255), */ + 0x75, 0x08, /* Report Size (8), */ + 0x95, 0x06, /* Report Count (6), */ + 0x80, /* Input, */ + 0xC0 /* End Collection */ +}; + static __u8 *uclogic_report_fixup(struct hid_device *hdev, __u8 *rdesc, unsigned int *rsize) { + struct usb_interface *iface = to_usb_interface(hdev->dev.parent); + __u8 iface_num = iface->cur_altsetting->desc.bInterfaceNumber; + switch (hdev->product) { case USB_DEVICE_ID_UCLOGIC_TABLET_PF1209: if (*rsize == PF1209_RDESC_ORIG_SIZE) { @@ -386,6 +503,28 @@ static __u8 *uclogic_report_fixup(struct hid_device *hdev, __u8 *rdesc, *rsize = sizeof(wp1062_rdesc_fixed); } break; + case USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850: + switch (iface_num) { + case 0: + if (*rsize == TWHL850_RDESC_ORIG_SIZE0) { + rdesc = twhl850_rdesc_fixed0; + *rsize = sizeof(twhl850_rdesc_fixed0); + } + break; + case 1: + if (*rsize == TWHL850_RDESC_ORIG_SIZE1) { + rdesc = twhl850_rdesc_fixed1; + *rsize = sizeof(twhl850_rdesc_fixed1); + } + break; + case 2: + if (*rsize == TWHL850_RDESC_ORIG_SIZE2) { + rdesc = twhl850_rdesc_fixed2; + *rsize = sizeof(twhl850_rdesc_fixed2); + } + break; + } + break; } return rdesc; @@ -402,6 +541,8 @@ static const struct hid_device_id uclogic_devices[] = { USB_DEVICE_ID_UCLOGIC_TABLET_WP8060U) }, { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, USB_DEVICE_ID_UCLOGIC_TABLET_WP1062) }, + { HID_USB_DEVICE(USB_VENDOR_ID_UCLOGIC, + USB_DEVICE_ID_UCLOGIC_WIRELESS_TABLET_TWHL850) }, { } }; MODULE_DEVICE_TABLE(hid, uclogic_devices); -- 1.7.10 |
From: Nikolai K. <sp...@gm...> - 2012-05-14 09:03:24
|
Hi Jay, On 05/14/2012 10:00 AM, Jay Ortiz wrote: > I have a vistablet Muse and am running Ubunto 12.04 LTS. > (3.2.0-24-generic) and am trying to get this tablet to work. > > under Xinput: > WALTOP Batteryless Tablet stylusid=9[slave pointer (2)] > WALTOP Batteryless Tablet eraserid=11[slave pointer (2)] > WALTOP Batteryless Tablet padid=12[slave pointer (2)] > > under lsusb: > Bus 002 Device 003: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet > > According to your development list the Waltop Sirius Battery Free Tablet > <http://sourceforge.net/apps/mediawiki/digimend/index.php?title=Waltop_Sirius_Battery_Free_Tablet> > driver seems to be currently in development.... If you have a driver in > the works can I beta test? I would love to get this tablet working in > Gimp.... Please try installing an appropriate kernel package we're distributing: http://sf.net/apps/mediawiki/digimend/?title=Kernel_packages After that, the tablet should work either with xf86-input-wacom or xf86-input-evdev. However, xf86-input-wacom won't support tilting, but xf86-input-evdev will (in most applications). OTOH, xf86-input-evdev won't support "eraser" button, but xf86-input-wacom will. Additionally, horizontal scrolling won't work for now and the resolution will be limited to 2000 LPI. Sincerely, Nick |
From: Jay O. <ja...@va...> - 2012-05-14 07:28:18
|
Hello, I have a vistablet Muse and am running Ubunto 12.04 LTS. (3.2.0-24-generic) and am trying to get this tablet to work. under Xinput: WALTOP Batteryless Tablet stylus id=9 [slave pointer (2)] WALTOP Batteryless Tablet eraser id=11 [slave pointer (2)] WALTOP Batteryless Tablet pad id=12 [slave pointer (2)] under lsusb: Bus 002 Device 003: ID 172f:0502 Waltop International Corp. Sirius Battery Free Tablet According to your development list the Waltop Sirius Battery Free Tablet<http://sourceforge.net/apps/mediawiki/digimend/index.php?title=Waltop_Sirius_Battery_Free_Tablet> driver seems to be currently in development.... If you have a driver in the works can I beta test? I would love to get this tablet working in Gimp.... Thanks! Ovidio |
From: Eduardo H. S. <hob...@gm...> - 2012-05-09 12:44:24
|
2012/5/7 Nikolai Kondrashov <sp...@gm...>: > Hi Eduardo, > > > On 05/06/2012 10:52 PM, Eduardo H. Silva wrote: >> >> I'm sorry for the late reply, I delayed to the following day to do >> what you asked, but then forgot. >> >> The usbhid-dump command, the one you originally linked to, gives the >> error: >> >> invalid option -- 'm' > > > Most distributions have older version of usbhid-dump. You could download > newer version at http://sf.net/apps/mediawiki/digimend/?title=Usbhid-dump > or you could use the older one by finding out your tablet bus number and > device address using lsusb and then supplying it to usbhid-dump as the > arguments. > > Sincerely, > Nick Thanks, I've compiled the newer version. Attaching the result of pressing the pen's buttons. Eduardo |
From: Nikolai K. <sp...@gm...> - 2012-05-08 20:46:35
|
On 05/08/2012 11:28 PM, Favux ... wrote: > On Tue, May 8, 2012 at 3:13 PM, Nikolai Kondrashov<sp...@gm...> wrote: >> On 05/08/2012 07:51 PM, Favux ... wrote: >>> You need the hid.ko, hid-kye.ko, usbhid.ko, and usbmouse.ko. >> >> Um, I wouldn't think you need usbmouse.ko, but I may be wrong. > > I didn't either and did not originally include it but victoria.s said > it was necessary. Otherwise her KYE tablet didn't work right. Now, this is interesting. I can't see how it could be the reason, even though her tablet *does* have a mouse. I guess there was some sort of a coincedence. Sincerely, Nick |
From: Favux ... <fav...@gm...> - 2012-05-08 20:28:54
|
On Tue, May 8, 2012 at 3:13 PM, Nikolai Kondrashov <sp...@gm...> wrote: > > On 05/08/2012 07:51 PM, Favux ... wrote: >> >> You need the hid.ko, hid-kye.ko, usbhid.ko, and usbmouse.ko. > > Um, I wouldn't think you need usbmouse.ko, but I may be wrong. I didn't either and did not originally include it but victoria.s said it was necessary. Otherwise her KYE tablet didn't work right. >> So the question that stopped me was could a newly compiled free standing >> module override one built into the kernel? > > > I'm pretty sure it wouldn't. I was worried about that. I saw some dkms stuff that seemed to indicate it might, but it wasn't real clear. Favux |
From: Nikolai K. <sp...@gm...> - 2012-05-08 20:13:53
|
Hi Favux, Robert, On 05/08/2012 07:51 PM, Favux ... wrote: > You need the hid.ko, hid-kye.ko, usbhid.ko, and usbmouse.ko. Um, I wouldn't think you need usbmouse.ko, but I may be wrong. > So the question that stopped me was could a newly compiled free standing > module override one built into the kernel? I'm pretty sure it wouldn't. Sincerely, Nick |
From: Robert A. <ro...@gm...> - 2012-05-08 17:17:47
|
On Tue, May 8, 2012 at 9:51 AM, Favux ... <fav...@gm...> wrote: > Hi Robert and Nick, > > Robert I did start duplicating the Ubuntu instructions in Fedora. I > can't find all my notes but... > > I got to the rpmbuild directory and was ready to patch when I realized > a few things. > > 1) The Fedora rpm kernel is a little more complicated to work with > than the Debian/Ubuntu kernel method. Which meant a more complicated > HOW TO. > 2) I didn't really have a place to host a Fedora HID kernel module HOW TO. > 3) The Fedora kernel team had chosen different HID modules to > build-in or leave as free standing modules. > > The latter you can see in the /rpmbuild/BUILD/kernel-`uname > -r`/linux-`uname -r`/configs file: > > CONFIG_HID_SUPPORT=y > CONFIG_HID=y > CONFIG_HIDRAW=y > > # > # USB Input Devices > # > CONFIG_USB_HID=y > CONFIG_HID_PID=y > CONFIG_USB_HIDDEV=y > > # > # Special HID drivers > # > ...... > CONFIG_HOLTEK_FF=y > CONFIG_HID_KEYTOUCH=m > CONFIG_HID_KYE=y > CONFIG_HID_UCLOGIC=m > CONFIG_HID_WALTOP=m > ...... > > You need the hid.ko, hid-kye.ko, usbhid.ko, and usbmouse.ko. The =y > means they are choosing to make for e.g. the KYE module a built-in, > where =m means a free standing module. Since they are treating > usbhid.ko as a built-in also (CONFIG_USB_HID=y) I felt a little > uncomfortable with trying to make it a fee-standing module. With > Ubuntu the ones we were interested in were all free standing so it > was easy to backup the original modules and not be worried about > compiling a patched module. I didn't really want the HOW TO turning > into a kernel compiling HOW TO. So the question that stopped me was > could a newly compiled free standing module override one built into > the kernel? I thought maybe it would but wasn't sure. If not then > you have to compile the entire kernel. I don't have a KYE tablet to > test and didn't have a Fedora tester like viktoria.s. > > Nick can probably tell us the answer to that question. Now that was > the 3.2 kernel and they're up to 3.3 now. The kernel team can change > what they decide to build-in or not so we'd have to look at that > again. > Thank you Nick and Favux, You have explained the situation perfectly. I now understand the reason I have to make a new kernel. Hmm. I might try it but it might just be easier for me to switch to Ubuntu 12.04 LTS. I like the 5 year support term as opposed to 1 year for Fedora. Thank you for your help. The prebuilt packages you guys supply for 12.04 will be much easier to apply. Cheers -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada |
From: Favux ... <fav...@gm...> - 2012-05-08 16:51:14
|
Hi Robert and Nick, Robert I did start duplicating the Ubuntu instructions in Fedora. I can't find all my notes but... I got to the rpmbuild directory and was ready to patch when I realized a few things. 1) The Fedora rpm kernel is a little more complicated to work with than the Debian/Ubuntu kernel method. Which meant a more complicated HOW TO. 2) I didn't really have a place to host a Fedora HID kernel module HOW TO. 3) The Fedora kernel team had chosen different HID modules to build-in or leave as free standing modules. The latter you can see in the /rpmbuild/BUILD/kernel-`uname -r`/linux-`uname -r`/configs file: CONFIG_HID_SUPPORT=y CONFIG_HID=y CONFIG_HIDRAW=y # # USB Input Devices # CONFIG_USB_HID=y CONFIG_HID_PID=y CONFIG_USB_HIDDEV=y # # Special HID drivers # ...... CONFIG_HOLTEK_FF=y CONFIG_HID_KEYTOUCH=m CONFIG_HID_KYE=y CONFIG_HID_UCLOGIC=m CONFIG_HID_WALTOP=m ...... You need the hid.ko, hid-kye.ko, usbhid.ko, and usbmouse.ko. The =y means they are choosing to make for e.g. the KYE module a built-in, where =m means a free standing module. Since they are treating usbhid.ko as a built-in also (CONFIG_USB_HID=y) I felt a little uncomfortable with trying to make it a fee-standing module. With Ubuntu the ones we were interested in were all free standing so it was easy to backup the original modules and not be worried about compiling a patched module. I didn't really want the HOW TO turning into a kernel compiling HOW TO. So the question that stopped me was could a newly compiled free standing module override one built into the kernel? I thought maybe it would but wasn't sure. If not then you have to compile the entire kernel. I don't have a KYE tablet to test and didn't have a Fedora tester like viktoria.s. Nick can probably tell us the answer to that question. Now that was the 3.2 kernel and they're up to 3.3 now. The kernel team can change what they decide to build-in or not so we'd have to look at that again. Favux P.S.: DIGImend and the rest are off-line on SourceForge currently so I can't check out your model. |
From: Nikolai K. <sp...@gm...> - 2012-05-08 07:37:34
|
Hi Robert, On 05/07/2012 11:44 PM, Robert Arkiletian wrote: > Thank you Nikolai that helped, but I can't get it to produce ink. > > I am on 2.6.35. So I got 2.6.35 source then applied digimend patches > for 2.6.32 manually by hand to hid-kye.c > > here is my hid-kye.c > > http://pastebin.com/8HLLDVaP > > after building and installing hid-kye.ko module it is recognised > > dmesg > > > [ 269.199124] usb 3-1: new full speed USB device using uhci_hcd and address 2 > [ 269.359016] usb 3-1: New USB device found, idVendor=0458, idProduct=5013 > [ 269.359022] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > [ 269.359027] usb 3-1: Product: EasyPen M610X > [ 269.359031] usb 3-1: Manufacturer: Genius > [ 269.379275] input: Genius EasyPen M610X as > /devices/pci0000:00/0000:00:1d.2/usb3/3-1/3-1:1.0/input/input4 > [ 269.379784] generic-usb 0003:0458:5013.0004: > input,hiddev97,hidraw3: USB HID v1.11 Device [Genius EasyPen M610X] on > usb-0000:00:1d.2-1/input0 The last line shows that the tablet is still handled by the generic HID driver. Did you patch and build "usbhid" and "hid" modules? The "hid" module is changed to list supported KYE tablets as having a specific driver. The "usbhid" module is changed to add quirks for two of the tablets, including yours. I think that these modules could only be built as part of a kernel build, because they require internal symbols. This is basically why we don't simply supply a kernel module package. This, however, will hopefully be changed with 3.5 kernel release. Although, this doesn't help users with older kernels, of course. Sincerely, Nick |
From: Robert A. <ro...@gm...> - 2012-05-07 20:44:54
|
On Sun, May 6, 2012 at 3:09 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Robert, > > > On 05/06/2012 04:23 AM, Robert Arkiletian wrote: >> >> there is instructions to build drivers here >> >> http://ubuntuforums.org/showthread.php?t=1946486 >> >> but I am on Red Hat based Fedora distro. Anyone know where there are >> Fedora specific instructions? > > > There are official instructions for building custom Fedora kernels: > > http://fedoraproject.org/wiki/Building_a_custom_kernel > > You need to follow them and apply DIGImend kernel patches in the process: > > https://sourceforge.net/apps/mediawiki/digimend/index.php?title=Kernel_patches > > Still, if there is enough demand we may start building Fedora kernels in > addition to the Ubuntu ones we already build: > > https://sourceforge.net/apps/mediawiki/digimend/index.php?title=Kernel_packages > > Sincerely, > Nick Thank you Nikolai that helped, but I can't get it to produce ink. I am on 2.6.35. So I got 2.6.35 source then applied digimend patches for 2.6.32 manually by hand to hid-kye.c here is my hid-kye.c http://pastebin.com/8HLLDVaP after building and installing hid-kye.ko module it is recognised dmesg [ 269.199124] usb 3-1: new full speed USB device using uhci_hcd and address 2 [ 269.359016] usb 3-1: New USB device found, idVendor=0458, idProduct=5013 [ 269.359022] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 269.359027] usb 3-1: Product: EasyPen M610X [ 269.359031] usb 3-1: Manufacturer: Genius [ 269.379275] input: Genius EasyPen M610X as /devices/pci0000:00/0000:00:1d.2/usb3/3-1/3-1:1.0/input/input4 [ 269.379784] generic-usb 0003:0458:5013.0004: input,hiddev97,hidraw3: USB HID v1.11 Device [Genius EasyPen M610X] on usb-0000:00:1d.2-1/input0 and xinput list-props 'Genius EasyPen M610X' Device 'Genius EasyPen M610X': Device Enabled (146): 1 Coordinate Transformation Matrix (148): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000 Device Accel Profile (267): 0 Device Accel Constant Deceleration (268): 1.000000 Device Accel Adaptive Deceleration (269): 1.000000 Device Accel Velocity Scaling (270): 10.000000 Evdev Axis Inversion (271): 0, 0 Evdev Axis Calibration (272): <no items> Evdev Axes Swap (273): 0 Axis Labels (274): "Abs X" (265), "Abs Y" (266), "Abs Z" (492), "Abs Rotary X" (493), "Abs Rotary Y" (494), "Abs Rotary Z" (495), "Abs Pressure" (496), "Abs Volume" (497) Button Labels (275): "Button Left" (149), "Button Middle" (150), "Button Right" (151), "Button Wheel Up" (152), "Button Wheel Down" (153), "Button Horiz Wheel Left" (154), "Button Horiz Wheel Right" (155), "Button Side" (489), "Button Extra" (490), "Button Forward" (491), "Button Unknown" (264), "Button Unknown" (264), "Button Unknown" (264), "Button Unknown" (264) Evdev Middle Button Emulation (276): 0 Evdev Middle Button Timeout (277): 50 Evdev Wheel Emulation (278): 0 Evdev Wheel Emulation Axes (279): 0, 0, 4, 5 Evdev Wheel Emulation Inertia (280): 10 Evdev Wheel Emulation Timeout (281): 200 Evdev Wheel Emulation Button (282): 4 Evdev Drag Lock Buttons (283): 0 It works somewhat. The pen movement is fine and I can left click but no ability to draw in any paint program. No ink. Any hints??? Thanks -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada |
From: Nikolai K. <sp...@gm...> - 2012-05-07 08:11:20
|
Hi Zauber, On 04/19/2012 11:51 PM, Zauber Paracelsus wrote: > Alright, thanks for the update, Nick :-) I think, my first guess was right and X.org is really just re-transforming the old values of missing axes. I've submitted an X.org bug: https://bugs.freedesktop.org/show_bug.cgi?id=49347 as I'm failing to find time to find a good fix for this, sorry. Hopefully, someone notices and fixes it in Git. Then we could backport the fix to your X.org version. Sorry for the delay. Sincerely, Nick |
From: Nikolai K. <sp...@gm...> - 2012-05-07 05:41:54
|
Hi Eduardo, On 05/06/2012 10:52 PM, Eduardo H. Silva wrote: > I'm sorry for the late reply, I delayed to the following day to do > what you asked, but then forgot. > > The usbhid-dump command, the one you originally linked to, gives the error: > > invalid option -- 'm' Most distributions have older version of usbhid-dump. You could download newer version at http://sf.net/apps/mediawiki/digimend/?title=Usbhid-dump or you could use the older one by finding out your tablet bus number and device address using lsusb and then supplying it to usbhid-dump as the arguments. Sincerely, Nick |
From: Eduardo H. S. <hob...@gm...> - 2012-05-06 19:52:36
|
2012/5/3 Nikolai Kondrashov <sp...@gm...>: > On 05/02/2012 10:55 PM, Eduardo H. Silva wrote: >> >> I'm attaching the outputs. > > > Thanks! This is unexpected. I see the kernel indeed reporting full pressure > on a side button click. This is something new. When I tested this model, it > didn't do such thing, so this must be a recent addition. I don't know the > purpose though. > > Could you please do the "pen buttons" test, but with usbhid-dump this time? > > I have a workaround for this behavior for the tablet with PID 0038. So, if > usbhid-dump verifies your tablet does the same thing, I will add its > handling there and will send you a kernel patch to test. > > Sincerely, > Nick I'm sorry for the late reply, I delayed to the following day to do what you asked, but then forgot. The usbhid-dump command, the one you originally linked to, gives the error: invalid option -- 'm' Removing the -m option, gives the error: Not enough arguments Just doing usbhid-dump --help, shows: Usage: usbhid-dump [OPTION]... <bus> <dev> [if] Dump a USB device HID report descriptor(s) and/or stream(s). Arguments: bus bus number (1-255) dev device address (1-255) if interface number (0-254); if omitted, all device HID interfaces are dumped Options: -h, --help this help message -e, --entity=STRING what to dump: either "descriptor", "stream" or "both"; value can be abbreviated -p, --stream-paused start with the stream dump output paused -f, --stream-feedback enable stream dumping feedback: for every transfer dumped a dot is printed to stderr Default options: --entity=descriptor Signals: USR1/USR2 pause/resume the stream dump output usbutils is at version 004-4. Eduardo |
From: Nikolai K. <sp...@gm...> - 2012-05-06 10:09:22
|
Hi Robert, On 05/06/2012 04:23 AM, Robert Arkiletian wrote: > there is instructions to build drivers here > > http://ubuntuforums.org/showthread.php?t=1946486 > > but I am on Red Hat based Fedora distro. Anyone know where there are > Fedora specific instructions? There are official instructions for building custom Fedora kernels: http://fedoraproject.org/wiki/Building_a_custom_kernel You need to follow them and apply DIGImend kernel patches in the process: https://sourceforge.net/apps/mediawiki/digimend/index.php?title=Kernel_patches Still, if there is enough demand we may start building Fedora kernels in addition to the Ubuntu ones we already build: https://sourceforge.net/apps/mediawiki/digimend/index.php?title=Kernel_packages Sincerely, Nick |
From: Robert A. <ro...@gm...> - 2012-05-06 01:23:19
|
there is instructions to build drivers here http://ubuntuforums.org/showthread.php?t=1946486 but I am on Red Hat based Fedora distro. Anyone know where there are Fedora specific instructions? Thanks -- Robert Arkiletian Eric Hamber Secondary, Vancouver, Canada |
From: Nikolai K. <sp...@gm...> - 2012-05-03 05:47:14
|
On 05/02/2012 10:55 PM, Eduardo H. Silva wrote: > I'm attaching the outputs. Thanks! This is unexpected. I see the kernel indeed reporting full pressure on a side button click. This is something new. When I tested this model, it didn't do such thing, so this must be a recent addition. I don't know the purpose though. Could you please do the "pen buttons" test, but with usbhid-dump this time? I have a workaround for this behavior for the tablet with PID 0038. So, if usbhid-dump verifies your tablet does the same thing, I will add its handling there and will send you a kernel patch to test. Sincerely, Nick |
From: Eduardo H. S. <hob...@gm...> - 2012-05-02 19:55:57
|
2012/5/1 Nikolai Kondrashov <sp...@gm...>: > Hi Dave, Eduardo, > > > On 04/30/2012 03:12 AM, Favux ... wrote: >> >> Assuming we don't have a driver problem and the stylus is on the Wacom >> X driver I'm thinking this is a kernel driver problem. What are your >> thoughts Nick? > > > Eduardo, to rule this out, could you please get some evtest output for the > stylus event device? You will probably need to run evtest in a text console, > because the Wacom driver grabs it under X. > > Please run "sudo evtest" and try to find out which event device corresponds > to the stylus, it will probably be the least numbered among Waltop devices > and it will produce output when moving the pen. > > After you've identified it, could you please capture and send here the > evtest output for the "pressure" and "buttons" parts of the "collecting > tablet diagnostics" HOWTO: > > http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Pressure > http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Buttons > > Please use "sudo evtest" in place of "sudo usbhid-dump ...". > > Meanwhile I'll try to find the time to install Fedora on a virtual machine > and try to reproduce you problem with Media Tablet 10.6, which is similar to > your model. > > Thanks! > > Sincerely, > Nick I'm attaching the outputs. Eduardo |
From: Nikolai K. <sp...@gm...> - 2012-05-01 12:19:38
|
Hi Dave, On 04/29/2012 09:22 PM, Favux ... wrote: > Your new Xorg.0.log shows that event10 is the stylus and is being set up > by Wacom while events 11, 12, and 13 are being claimed by evdev. I think > that is correct, Nick can tell us. Yes, I think this is the best way to set it up. Sincerely, Nick |
From: Nikolai K. <sp...@gm...> - 2012-05-01 12:16:45
|
Hi Dave, Eduardo, On 04/30/2012 03:12 AM, Favux ... wrote: > Assuming we don't have a driver problem and the stylus is on the Wacom > X driver I'm thinking this is a kernel driver problem. What are your > thoughts Nick? Eduardo, to rule this out, could you please get some evtest output for the stylus event device? You will probably need to run evtest in a text console, because the Wacom driver grabs it under X. Please run "sudo evtest" and try to find out which event device corresponds to the stylus, it will probably be the least numbered among Waltop devices and it will produce output when moving the pen. After you've identified it, could you please capture and send here the evtest output for the "pressure" and "buttons" parts of the "collecting tablet diagnostics" HOWTO: http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Pressure http://sf.net/apps/mediawiki/digimend/?title=Collecting_tablet_diagnostics#Buttons Please use "sudo evtest" in place of "sudo usbhid-dump ...". Meanwhile I'll try to find the time to install Fedora on a virtual machine and try to reproduce you problem with Media Tablet 10.6, which is similar to your model. Thanks! Sincerely, Nick |
From: Favux ... <fav...@gm...> - 2012-04-30 14:21:48
|
Hi, There's a bit of disagreement on the LWP project. Either Waltop tablets with their stylus on the xf86-input-wacom driver are suppose to show up in Wacom Graphics Tablet applet as a generic stylus without details (what I thought had been happening) or they now need a libwacom tablet data file first. The libwacom page on the LWP mediawiki shows a sample data file: http://sourceforge.net/apps/mediawiki/linuxwacom/index.php?title=Libwacom But either way we should probably submit Waltop data files. Favux |
From: Nicodem <nic...@gm...> - 2012-04-30 06:47:23
|
thanks! All good. On Sat, Apr 28, 2012 at 6:51 PM, Nikolai Kondrashov <sp...@gm...>wrote: > Hi Dominik, > > > On 04/27/2012 11:16 AM, Nicodem wrote: > >> today Ive updated my Ubuntu to 12.04 official and now I have 3.2.0-24 >> kernel. >> Any chance for patches? :) >> > > Please download the updated kernels at the usual location: > https://sourceforge.net/**projects/digimend/files/** > kernel-packages/kernel-**patches-5/<https://sourceforge.net/projects/digimend/files/kernel-packages/kernel-patches-5/> > > Sincerely, > Nick > |