digimend-devel Mailing List for DIGImend (Page 4)
Brought to you by:
spb_nick
Menu
▾
▴
digimend-devel — Development matters
You can subscribe to this list here.
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
(27) |
Jul
(54) |
Aug
(54) |
Sep
(13) |
Oct
(20) |
Nov
(7) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2013 |
Jan
(3) |
Feb
(3) |
Mar
(6) |
Apr
(1) |
May
(8) |
Jun
(5) |
Jul
(4) |
Aug
(10) |
Sep
(44) |
Oct
(12) |
Nov
(5) |
Dec
(14) |
| 2014 |
Jan
(16) |
Feb
(3) |
Mar
(3) |
Apr
(5) |
May
(2) |
Jun
(14) |
Jul
(38) |
Aug
(15) |
Sep
(15) |
Oct
(12) |
Nov
(38) |
Dec
(31) |
| 2015 |
Jan
(73) |
Feb
(71) |
Mar
(57) |
Apr
(36) |
May
(33) |
Jun
(20) |
Jul
(4) |
Aug
(5) |
Sep
(1) |
Oct
(11) |
Nov
(2) |
Dec
(6) |
| 2016 |
Jan
(7) |
Feb
(3) |
Mar
(6) |
Apr
(2) |
May
(7) |
Jun
(5) |
Jul
(3) |
Aug
(5) |
Sep
(5) |
Oct
(8) |
Nov
(13) |
Dec
|
|
From: lukman <ada...@gm...> - 2015-08-26 00:17:36
|
M 55 00 43 00 2D 00 4C 00 6F 00 67 00 69 00 63 00
P 50 00 45 00 4E 00 20 00 54 00 41 00 42 00 4C 00 45 00 54 00 20 00
S 64 0C 03 00 7D 20 4E 03 00 FF 07 A0 0F
S 65 04 03 20 A0
S 6E 04 03 30 00
S 79 1A 03 32 00 30 00 31 00 33 00 31 00 32 00 30 00 32 00 20 00 4F 00 53 00 43 00
S 7A 08 03 01 03 01 00 00 00
S 7B 0C 03 48 00 4B 00 20 00 4F 00 6E 00
uclogic-decode:
Manufacturer: UC-Logic
Product: PEN TABLET
Max X: 32000
Max Y: 20000
Max pressure: 2047
Resolution: 4000
Internal model: 20131202 OSC
Buttons status: HK On
|
|
From: Marjan I. <mar...@gm...> - 2015-08-04 23:21:38
|
Hello there, >From yesterday I'm linux user. I've set everything except this one. The Huion H610 driver. I have followed the steps from here <https://github.com/DIGImend/digimend-kernel-drivers>, but still it doesn't work. I have the latest stable kernel -> 4.1.4. How can I solve the problem? Hope to hear from you soon, Marjan |
|
From: Nikolai K. <sp...@gm...> - 2015-07-22 08:00:44
|
On 07/20/2015 06:37 PM, yoquesé nosecomo wrote: > Hi, > > Since last week I've tested the v5 release in another computer with elementary OS with the same effect. Today, I've tested the current development version in a fresh install of mint, and it worked! The stylus input goes to a pen device and the frame buttons go to a pad device, as they should. However, now I have 6 HUION devices, 4 of which don't give any events, I dont know if that is necessarily bad, it just looks a little strange to me. > > The thing is, I want to assign the frame buttons to specific actions in krita but I can't. Is that because they are slave to "Virtual core pointer" in xinput? Would they work if they were slave to the core keyboard and I gave them a keycode (not sure if it is the correct term) which isn't in my keyboard? I tried but it seems you cant assign any device as slave. Maybe I could use xbindkeys and xte as a workaround to this as in here <http://forums.logitech.com/t5/Mice-and-Pointing-Devices/Guide-for-setup-Performance-MX-mouse-on-Linux-with-KDE/td-p/517167>, but I don't want to throw in too many things. > > I will paste here the output of xinput, I can run the diagnostics again, If you would like to. > > xinput: > > ⎡ Virtual core pointer id=2 [master pointer (3)] > ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] > ⎜ ↳ HUION H58L Pen id=11 [slave pointer (2)] > ⎜ ↳ HUION H58L Pad id=12 [slave pointer (2)] > ⎜ ↳ HUION H58L Mouse id=13 [slave pointer (2)] > ⎜ ↳ HUION H58L Consumer Control id=15 [slave pointer (2)] > ⎜ ↳ Logitech USB Receiver id=17 [slave pointer (2)] > ⎜ ↳ Logitech USB Receiver id=18 [slave pointer (2)] > ⎜ ↳ AlpsPS/2 ALPS GlidePoint id=21 [slave pointer (2)] > ⎜ ↳ ALPS PS/2 Device id=22 [slave pointer (2)] > ⎣ Virtual core keyboard id=3 [master keyboard (2)] > ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] > ↳ Power Button id=6 [slave keyboard (3)] > ↳ Video Bus id=7 [slave keyboard (3)] > ↳ Video Bus id=8 [slave keyboard (3)] > ↳ Power Button id=9 [slave keyboard (3)] > ↳ Sleep Button id=10 [slave keyboard (3)] > ↳ HUION H58L Keyboard id=14 [slave keyboard (3)] > ↳ HUION H58L System Control id=16 [slave keyboard (3)] > ↳ Laptop_Integrated_Webcam_HD id=19 [slave keyboard (3)] > ↳ AT Translated Set 2 keyboard id=20 [slave keyboard (3)] > ↳ Dell WMI hotkeys id=23 [slave keyboard (3)] Ah, I somehow assumed you were running latest master already. Glad to hear it works. From your xinput output I can see that you're using the xf86-input-evdev driver. To get the configurable buttons to work, please try using the xf86-input-wacom driver. Use xsetwacom to configure the bindings. The pad device appears under "Virtual core pointer" to cater to the Wacom driver for now. Nick |
|
From: yoquesé n. <por...@gm...> - 2015-07-15 14:02:58
|
Hello Nikolai, The system is a recently installed linux mint 17.2, with linux kernel version 3.16.0-38-generic. I followed the instructions on your web, between different command I had to reconnect the tablet though, it said the resource was busy, but this didn't have any effect in the results as far as i know. modinfo hid-huion gave me this: filename: /lib/modules/3.16.0-38-generic/extra/hid-huion.ko version: 5 license: GPL description: Huion HID driver author: Nikolai Kondrashov author: Martin Rusko srcversion: AA341FE887649B154C7BB63 alias: hid:b0003g*v00005543p0000004D alias: hid:b0003g*v00005543p0000006E alias: hid:b0003g*v0000256Cp0000006E depends: hid vermagic: 3.16.0-38-generic SMP mod_unload modversions The three interfaces appeared after installing digimend, previously there was only one, but it only recognised the stylus. /dev/input/event16: HUION H58L /dev/input/event17: HUION H58L /dev/input/event18: HUION H58L And xinput (IDs vary): ↳ HUION H58L id=11 [slave pointer (2)] ↳ HUION H58L id=12 [slave pointer (2)] ↳ HUION H58L id=13 [slave pointer (2)] Thanks for the reply! 2015-07-15 14:08 GMT+02:00 Nikolai Kondrashov <sp...@gm...>: > Hello Yoquesé, > > On 07/12/2015 10:31 PM, yoquesé nosecomo wrote: > >> Is there any way to configure the key mapping on a non-wacom tablet? >> The tablet works fine (great work on that!), but i would rather reassign >> the 6 buttons in the huion H58L. >> >> I have tried to use xinput but it doesn't work, I even tried xsetwacom >> but then the buttons wouldn't work at all. >> >> ( actually, using xsetwacom to change the buttons gave me this error: >> Invalid offset into Wacom Button Actions property ) >> >> The keycodes i get from pressing the buttons from top to bottom are: >> >> 26 >> 37,52 >> 37,50,57 >> 2 >> 3 >> 4 >> > > The diagnostics (frame_buttons.txt file) looks really weird: the tablet is > sending different buttons over three different interfaces. I haven't seen > anything like that from Huion before. How was that dump taken? Was it on a > system the driver already installed? > > I have attached the result from the diagnostics and uclogic-probe. >> > > Thanks for the diagnostics! One thing though: could you please send raw > uclogic-probe data, not decoded with uclogic-decode? Thank you. > > EDIT: Seems I have mistakenly sent this to the support forum with the >> attachments and made a mess, sorry for that :P >> > > No problem :) > > Nick > > P.S. Please keep maillist in the CC - use "Reply to All" when replying. > |
|
From: Nikolai K. <sp...@gm...> - 2015-07-15 12:09:10
|
Hello Yoquesé, On 07/12/2015 10:31 PM, yoquesé nosecomo wrote: > Is there any way to configure the key mapping on a non-wacom tablet? > The tablet works fine (great work on that!), but i would rather reassign the 6 buttons in the huion H58L. > > I have tried to use xinput but it doesn't work, I even tried xsetwacom but then the buttons wouldn't work at all. > > ( actually, using xsetwacom to change the buttons gave me this error: > Invalid offset into Wacom Button Actions property ) > > The keycodes i get from pressing the buttons from top to bottom are: > > 26 > 37,52 > 37,50,57 > 2 > 3 > 4 The diagnostics (frame_buttons.txt file) looks really weird: the tablet is sending different buttons over three different interfaces. I haven't seen anything like that from Huion before. How was that dump taken? Was it on a system the driver already installed? > I have attached the result from the diagnostics and uclogic-probe. Thanks for the diagnostics! One thing though: could you please send raw uclogic-probe data, not decoded with uclogic-decode? Thank you. > EDIT: Seems I have mistakenly sent this to the support forum with the attachments and made a mess, sorry for that :P No problem :) Nick P.S. Please keep maillist in the CC - use "Reply to All" when replying. |
|
From: yoquesé n. <por...@gm...> - 2015-07-12 19:32:21
|
Bus 003 Device 004: ID 256c:006e
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x256c
idProduct 0x006e
bcdDevice 0.00
iManufacturer 5 HUION
iProduct 6 H58L
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 84
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.0b
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 177
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 244
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 2
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.0b
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 92
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 8
Device Status: 0x0000
(Bus Powered) |
|
From: Ashwyn F. <as...@gm...> - 2015-06-29 19:04:15
|
Sorry about the HTML message before, here is the plaintext of what I wrote: "Hey again, I'm attaching more recent diagnostics for the H850S tablet, aka Lapäzz TWH850, or 5543:0782 UC-Logic Technology Corp. Its been collecting dust under my couch for a long time, but I thought I'd check out the progress and was pleasantly surprised that it appears to interact reasonably well with Gnome 3.16 on fedora 22. The pen moves the cursor perfectly well, and gnome recognises when I click with the pen tip to launch the activities view, or click on menus, but not when I click to launch a program... It seems that a lot of work has been done to support the model number 5534:0781, and I'm hoping that it is not a huge jump to get my model working... the visual appearance of my tablet is almost identical to the 5534:0781 v2 and v3, only without a mouse." |
|
From: Ashwyn F. <as...@gm...> - 2015-06-29 18:41:25
|
Bus 002 Device 005: ID 5543:0782 UC-Logic Technology Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x5543 UC-Logic Technology Corp.
idProduct 0x0782
bcdDevice 0.00
iManufacturer 1
iProduct 2 H850S
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 59
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 300mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 254
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 5
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 139
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 10
Device Status: 0x0000
(Bus Powered) |
|
From: Nikolai K. <sp...@gm...> - 2015-06-22 10:32:31
|
On 06/22/2015 02:27 AM, Martin Shepherd wrote: > I have attached the results of running uclogic-probe on the tablet. > When I pass this to uclogic-decode, I see the following: > > Manufacturer: UC-LOGIC > Product: TWHA60 > Max X: 40000 > Max Y: 25000 > Max pressure: 2047 > Resolution: 4000 > Internal model: HA60-F401 > Buttons status: HK On Ah, wonderful! So the buttons work. I pushed a small change to the driver, it is now in latest master. Now to use the frame buttons you will have to use xf86-input-wacom driver with your tablet, which will let you configure the shortcuts, pressure curve, rotation, etc. with xsetwacom, if not the gnome tablet app. There is no good HOWTO at the moment (contributions welcome!), but basically you have to set up an Xorg.conf snippet assigning xf86-input-wacom to all of your tablet event devices, or perhaps the "Pad" and "Pen" ones at least. This rather old HOWTO can help a bit: http://digimend.github.io/support/howto/drivers/wacom/ Nick |
|
From: GitHub <no...@gi...> - 2015-06-22 10:24:18
|
Branch: refs/heads/master Home: https://github.com/DIGImend/digimend-kernel-drivers Commit: 65ae046bfa5c92ba3e1e516ed4b378a800c5b724 https://github.com/DIGImend/digimend-kernel-drivers/commit/65ae046bfa5c92ba3e1e516ed4b378a800c5b724 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-22 (Mon, 22 Jun 2015) Changed paths: M hid-uclogic.c Log Message: ----------- uclogic: Add button enabling for TWHA60 v3 |
|
From: Martin S. <mcs...@gm...> - 2015-06-21 23:27:27
|
I have attached the results of running uclogic-probe on the tablet.
When I pass this to uclogic-decode, I see the following:
Manufacturer: UC-LOGIC
Product: TWHA60
Max X: 40000
Max Y: 25000
Max pressure: 2047
Resolution: 4000
Internal model: HA60-F401
Buttons status: HK On
On Sat, Jun 20, 2015 at 2:59 AM, Nikolai Kondrashov <sp...@gm...> wrote:
> Hi Martin,
>
> On 06/20/2015 04:50 AM, Martin Shepherd wrote:
>>
>> Your latest version of the driver appears to work perfectly. In
>> inkscape both motion and pressure sensitivity work well.
>>
>> There was one problem when I first tested it. When I first loaded the
>> driver my synaptics touchpad stopped responding to taps, and I had to
>> reload the psmouse driver to resolve that. However since then, I've
>> tried unloading and reloading the usbhid and hid_uclogic drivers a few
>> times, and I haven't been able to reproduce the problem with the
>> synaptics touch-pad. I also checked that after a reboot, that both the
>> tablet and the synaptics touch-pad worked properly.
>>
>> Thank you for porting the driver to this tablet.
>
>
> You're welcome! Glad to hear it worked finally. Not sure what to make of the
> synaptics issue.
>
> Now, we can try to make the buttons on the frame compatible with
> xf86-input-wacom driver. If you'd like to do that, please run
> uclogic-probe [1] on your tablet and send the output. Thank you.
>
> Nick
>
> [1] https://github.com/DIGImend/uclogic-tools
|
|
From: Nikolai K. <sp...@gm...> - 2015-06-20 09:59:51
|
Hi Martin, On 06/20/2015 04:50 AM, Martin Shepherd wrote: > Your latest version of the driver appears to work perfectly. In > inkscape both motion and pressure sensitivity work well. > > There was one problem when I first tested it. When I first loaded the > driver my synaptics touchpad stopped responding to taps, and I had to > reload the psmouse driver to resolve that. However since then, I've > tried unloading and reloading the usbhid and hid_uclogic drivers a few > times, and I haven't been able to reproduce the problem with the > synaptics touch-pad. I also checked that after a reboot, that both the > tablet and the synaptics touch-pad worked properly. > > Thank you for porting the driver to this tablet. You're welcome! Glad to hear it worked finally. Not sure what to make of the synaptics issue. Now, we can try to make the buttons on the frame compatible with xf86-input-wacom driver. If you'd like to do that, please run uclogic-probe [1] on your tablet and send the output. Thank you. Nick [1] https://github.com/DIGImend/uclogic-tools |
|
From: Martin S. <mcs...@gm...> - 2015-06-20 01:50:45
|
Hi Nick, Your latest version of the driver appears to work perfectly. In inkscape both motion and pressure sensitivity work well. There was one problem when I first tested it. When I first loaded the driver my synaptics touchpad stopped responding to taps, and I had to reload the psmouse driver to resolve that. However since then, I've tried unloading and reloading the usbhid and hid_uclogic drivers a few times, and I haven't been able to reproduce the problem with the synaptics touch-pad. I also checked that after a reboot, that both the tablet and the synaptics touch-pad worked properly. Thank you for porting the driver to this tablet. Martin On Fri, Jun 19, 2015 at 5:47 AM, Nikolai Kondrashov <sp...@gm...> wrote: > Hi Martin, > > On 06/18/2015 08:18 AM, Martin Shepherd wrote: >> >> I have attached 5 files. The first contains the output of dmesg when I >> plugged in the tablet. Note that the driver seems to find two pens. >> One of these is linked to /dev/input/event13, which appears to be the >> one that works, while the other is linked to /dev/input/event15, which >> doesn't produce any events. The second of the attached files shows the >> output of evtest on /dev/input/event13 while I was moving the pen >> horizontally from left to right. The third attachment shows the output >> from the same device when moving the pen vertically from top to >> bottom. The 4th and 5th attachments do the same for >> /dev/input/event15, which identifies itself as being a pen, but >> doesn't report any events when the pen is being moved. I hope that >> this helps. > > > Thanks, yes this helps! I've added in-range bit reversal to TWHA60 and added > ignoring fake pen usages, so you should have your cursor move and extra pen > interface disappear now. Please try the latest master. > > Thank you. > > Nick > > P.S. I wonder how did we manage to make that driver work when we added > TWHA60 > v3 support originally? Perhaps it has simply regressed. > > P.P.S. You can use "Reply to all" instead of "Reply" when replying to > automatically keep the maillist in CC. |
|
From: Prashant G. <pra...@ho...> - 2015-06-19 16:10:14
|
Hi Nick. I was wondering if anything can be done for my tablet's buttons and wheel. Also, how to determine the min and max values to constrain the tablet space according to the screen size? I read the process you sent me before but I cant figure out the required values and their units (mm? inches? dots?). Hope I am not bothering you. :P Regards, Prashant ---------------------------------------- > Hi Prashant, > > On 05/11/2015 09:53 PM, Prashant Gawande wrote: >> Also Nick, can you tell me how to set the aspect ratio/usable area of the >> pen tab according to the screen? Mine is 3/4 CRT and the pen tab is more >> towards 16/9 roughly. So I've to draw an oval physically to get a circle. > > Take a look at our xf86-input-evdev driver setup HOWTO: > http://digimend.github.io/support/howto/drivers/evdev/&calibration > > Nick ---------------------------------------- > From: pra...@ho... > To: sp...@gm...; dig...@li... > Subject: RE: [DIGImend-devel] iBall PF1064U Pen Tablet not working on Linux Mint 17.1 Xfce > Date: Tue, 12 May 2015 00:23:47 +0530 > > Also Nick, can you tell me how to set the aspect ratio/usable area of the pen tab according to the screen? Mine is 3/4 CRT and the pen tab is more towards 16/9 roughly. So I've to draw an oval physically to get a circle. > > ---------------------------------------- >> From: pra...@ho... >> To: sp...@gm...; dig...@li... >> Subject: RE: [DIGImend-devel] iBall PF1064U Pen Tablet not working on Linux Mint 17.1 Xfce >> Date: Mon, 11 May 2015 22:24:35 +0530 >> >> Hi Nick, >> >> Here's the diagnostics attached as an archive(8 files). Excuse me for the delay as there had been some power issues at my place. By the way, I tried the xinput button map trick; unfortunately; I couldn't figure it out precisely. But it's not that important at the moment. I need my frame buttons to work at first :P. Thanks for your constant support Nick. Regards. >> >> ---------------------------------------- >>> Date: Sun, 10 May 2015 22:40:07 +0300 >>> From: sp...@gm... >>> To: pra...@ho...; dig...@li... >>> Subject: Re: [DIGImend-devel] iBall PF1064U Pen Tablet not working on Linux Mint 17.1 Xfce >>> >>> Hi Prashant, >>> >>> On 05/10/2015 10:14 PM, Prashant Gawande wrote: >>>> Firstly, thanks a COSMIC ton for your efforts and support. And YES... I've >>>> pressure sensitivity, thanks to you again :). I'll send you all the >>>> diagnostics soon. Meanwhile, is it possible to swap functions of pen >>>> buttons? Right now, the lower button acts like middle and the upper button >>>> acts like right click. Is it possible to make it other way around? >>> >>> Yes, there are several methods, AFAIK. You can use "xinput --set-button-map". >>> See xinput manual page. Here, for example: >>> >>> http://www.x.org/archive/current/doc/man/man1/xinput.1.xhtml >>> >>> Nick >> > |
|
From: Nikolai K. <sp...@gm...> - 2015-06-19 12:47:25
|
Hi Martin,
On 06/18/2015 08:18 AM, Martin Shepherd wrote:
> I have attached 5 files. The first contains the output of dmesg when I
> plugged in the tablet. Note that the driver seems to find two pens.
> One of these is linked to /dev/input/event13, which appears to be the
> one that works, while the other is linked to /dev/input/event15, which
> doesn't produce any events. The second of the attached files shows the
> output of evtest on /dev/input/event13 while I was moving the pen
> horizontally from left to right. The third attachment shows the output
> from the same device when moving the pen vertically from top to
> bottom. The 4th and 5th attachments do the same for
> /dev/input/event15, which identifies itself as being a pen, but
> doesn't report any events when the pen is being moved. I hope that
> this helps.
Thanks, yes this helps! I've added in-range bit reversal to TWHA60 and added
ignoring fake pen usages, so you should have your cursor move and extra pen
interface disappear now. Please try the latest master.
Thank you.
Nick
P.S. I wonder how did we manage to make that driver work when we added TWHA60
v3 support originally? Perhaps it has simply regressed.
P.P.S. You can use "Reply to all" instead of "Reply" when replying to
automatically keep the maillist in CC.
|
|
From: GitHub <no...@gi...> - 2015-06-19 12:43:41
|
Branch: refs/heads/master Home: https://github.com/DIGImend/digimend-kernel-drivers Commit: 61b26ac19a81e78c4dde389191798e6556e92907 https://github.com/DIGImend/digimend-kernel-drivers/commit/61b26ac19a81e78c4dde389191798e6556e92907 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-19 (Fri, 19 Jun 2015) Changed paths: M hid-uclogic.c Log Message: ----------- uclogic: Invert in-rage bit for TWHA60 v3 Commit: e2d3d9884a07a40533d8bc413d81c3ed8f6685ea https://github.com/DIGImend/digimend-kernel-drivers/commit/e2d3d9884a07a40533d8bc413d81c3ed8f6685ea Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-19 (Fri, 19 Jun 2015) Changed paths: M hid-uclogic.c Log Message: ----------- uclogic: Ignore fake pen usages on TWHA60 Compare: https://github.com/DIGImend/digimend-kernel-drivers/compare/916dd3cd941f...e2d3d9884a07 |
|
From: Nikolai K. <sp...@gm...> - 2015-06-16 09:01:36
|
On 06/16/2015 05:47 AM, Martin Shepherd wrote: > I forgot to include digimend-devel in the list of recipients, so > here's the email again. > > Hi Nick, > > On Sun, Jun 14, 2015 at 2:59 AM, Nikolai Kondrashov <sp...@gm...> wrote: >> On 06/11/2015 05:02 AM, Martin Shepherd wrote: >>> >>> Done. I rebooted after doing this, then plugged in the tablet. I've >>> attached the output of dmesg from >>> just after plugging in the tablet, so that you can see the traceback >>> at the end. I've also attached a tar file >>> of the hid-uclogic.* files. Note that I did this with the latest >>> Ubuntu kernel (3.13.0-54-generic), >>> which is one version higher than the kernel that I tested with before. >> >> >> Thanks a lot, Martin! I tracked this down to my mistake of retrieving the >> USB >> device pointer incorrectly. I pushed a fix for this and also for report >> descriptor generation for your device. Please try latest master: >> >> https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip >> >> Nick > > Thanks. This fixed the crash, but unfortunately it didn't fix the > original problem. The fixed driver now behaves like the hid-uclogic.c > driver that came with the ubuntu kernel. The tip of the pen acts like > a switch, but there's no X,Y motion. Thanks for trying it! Could you please send the "dmesg" output after plugging the tablet in, and output of "evtest" for the pen device, where you do a stroke with the pen? Thank you. Nick |
|
From: Martin S. <mcs...@gm...> - 2015-06-16 02:47:35
|
I forgot to include digimend-devel in the list of recipients, so here's the email again. Hi Nick, On Sun, Jun 14, 2015 at 2:59 AM, Nikolai Kondrashov <sp...@gm...> wrote: > On 06/11/2015 05:02 AM, Martin Shepherd wrote: >> >> Done. I rebooted after doing this, then plugged in the tablet. I've >> attached the output of dmesg from >> just after plugging in the tablet, so that you can see the traceback >> at the end. I've also attached a tar file >> of the hid-uclogic.* files. Note that I did this with the latest >> Ubuntu kernel (3.13.0-54-generic), >> which is one version higher than the kernel that I tested with before. > > > Thanks a lot, Martin! I tracked this down to my mistake of retrieving the > USB > device pointer incorrectly. I pushed a fix for this and also for report > descriptor generation for your device. Please try latest master: > > https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > > Nick Thanks. This fixed the crash, but unfortunately it didn't fix the original problem. The fixed driver now behaves like the hid-uclogic.c driver that came with the ubuntu kernel. The tip of the pen acts like a switch, but there's no X,Y motion. Thanks, Martin |
|
From: GitHub <no...@gi...> - 2015-06-14 18:11:50
|
Branch: refs/heads/master Home: https://github.com/DIGImend/digimend-kernel-drivers Commit: 76e09fdd5b6a5b289e6a4907765989c31693e5b9 https://github.com/DIGImend/digimend-kernel-drivers/commit/76e09fdd5b6a5b289e6a4907765989c31693e5b9 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-14 (Sun, 14 Jun 2015) Changed paths: M README.md Log Message: ----------- Replace README.md tablet list with a link Replace tablet compatibility list in README.md with a link to the list on the website. Commit: 09407b6ac96e03e6de9047f2d03ec6188a073bee https://github.com/DIGImend/digimend-kernel-drivers/commit/09407b6ac96e03e6de9047f2d03ec6188a073bee Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-14 (Sun, 14 Jun 2015) Changed paths: M README.md Log Message: ----------- Do not mention pull requests in README.md to avoid confusion Commit: 916dd3cd941ffa455b99e34bf6f7cda606fa1ec8 https://github.com/DIGImend/digimend-kernel-drivers/commit/916dd3cd941ffa455b99e34bf6f7cda606fa1ec8 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-14 (Sun, 14 Jun 2015) Changed paths: M README.md Log Message: ----------- Drop reference to huion-driver from README.md as unnecessary Compare: https://github.com/DIGImend/digimend-kernel-drivers/compare/29b958cec5a5...916dd3cd941f |
|
From: Nikolai K. <sp...@gm...> - 2015-06-14 10:00:20
|
On 06/11/2015 05:02 AM, Martin Shepherd wrote: > Done. I rebooted after doing this, then plugged in the tablet. I've > attached the output of dmesg from > just after plugging in the tablet, so that you can see the traceback > at the end. I've also attached a tar file > of the hid-uclogic.* files. Note that I did this with the latest > Ubuntu kernel (3.13.0-54-generic), > which is one version higher than the kernel that I tested with before. Thanks a lot, Martin! I tracked this down to my mistake of retrieving the USB device pointer incorrectly. I pushed a fix for this and also for report descriptor generation for your device. Please try latest master: https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip Nick |
|
From: GitHub <no...@gi...> - 2015-06-14 09:56:51
|
Branch: refs/heads/master Home: https://github.com/DIGImend/digimend-kernel-drivers Commit: f70f8323462819379cf931bb3dc9f2ad721bc134 https://github.com/DIGImend/digimend-kernel-drivers/commit/f70f8323462819379cf931bb3dc9f2ad721bc134 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-07 (Sun, 07 Jun 2015) Changed paths: M hid-uclogic.c Log Message: ----------- uclogic: Let generated descriptors override constant Make uclogic_report_fixup override constant descriptors with generated descriptors, so models reusing product ID, but working with generated descriptor get correct one. This fixes TWHA60 descriptor assignment. Commit: 77a5544ce4e65352b82820260df5cfb74d361715 https://github.com/DIGImend/digimend-kernel-drivers/commit/77a5544ce4e65352b82820260df5cfb74d361715 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-07 (Sun, 07 Jun 2015) Changed paths: M hid-ids.h M hid-uclogic.c Log Message: ----------- uclogic: Rename Ugee 3031 to its OEM name of DrawImage G3 Commit: 29b958cec5a5f00437df2ea6dcf5aaa98f0df252 https://github.com/DIGImend/digimend-kernel-drivers/commit/29b958cec5a5f00437df2ea6dcf5aaa98f0df252 Author: Nikolai Kondrashov <sp...@gm...> Date: 2015-06-14 (Sun, 14 Jun 2015) Changed paths: M hid-uclogic.c Log Message: ----------- uclogic: Fix USB device retrieval in uclogic_probe Retrieve USB device corresponding to the HID device in uclogic_probe using hid_to_usb_dev, instead of incorrectly using to_usb_device on the interface sysfs device pointer. Compare: https://github.com/DIGImend/digimend-kernel-drivers/compare/ba1096eb251d...29b958cec5a5 |
|
From: Martin S. <mcs...@gm...> - 2015-06-11 02:02:39
|
On Mon, Jun 8, 2015 at 12:56 PM, Nikolai Kondrashov <sp...@gm...> wrote: > On 06/08/2015 10:09 PM, Nikolai Kondrashov wrote: >> >> On 06/08/2015 08:32 AM, Martin Shepherd wrote: >>> >>> Hi Nick, >>> >>> On Sun, Jun 7, 2015 at 6:31 AM, Nikolai Kondrashov <sp...@gm...> >>> wrote: >>>> >>>> Can you send hid-uclogic.* files from your build? Especially >>>> hid-uclogic.o. >>> >>> >>> I've attached a tar file containing them to this email. >>> >>>> I'll try this on Ubuntu myself with the version of the kernel you're >>>> using. >>>> Which version of Ubuntu is that? >>> >>> >>> 3.13.0-53-generic >>> >>> Thanks for the help. >> >> >> Thanks, Martin! >> >> Argh, these don't have the debugging information and I'm not sure how to >> enable debug info for an out-of-tree module. >> >> I'll try to guess which version of Ubuntu you're using and will try it >> myself. > > > Alright, I poked around a little and the issue doesn't reproduce with the > Huion tablet I have. I found how to enable debug info for the modules you > build so the traceback can be more useful. > > Could you please put this at the beginning of the makefile: > > ccflags-y := -g3 > > recompile, reinstall the modules, plug the tablet in and send me the new > traceback from dmesg, plus hid-uclogic.* files again? > > To recompile and reinstall you can use these commands: > > make clean > make > sudo make install Done. I rebooted after doing this, then plugged in the tablet. I've attached the output of dmesg from just after plugging in the tablet, so that you can see the traceback at the end. I've also attached a tar file of the hid-uclogic.* files. Note that I did this with the latest Ubuntu kernel (3.13.0-54-generic), which is one version higher than the kernel that I tested with before. Thank you, Martin |
|
From: Nikolai K. <sp...@gm...> - 2015-06-08 19:56:51
|
On 06/08/2015 10:09 PM, Nikolai Kondrashov wrote:
> On 06/08/2015 08:32 AM, Martin Shepherd wrote:
>> Hi Nick,
>>
>> On Sun, Jun 7, 2015 at 6:31 AM, Nikolai Kondrashov <sp...@gm...> wrote:
>>> Can you send hid-uclogic.* files from your build? Especially hid-uclogic.o.
>>
>> I've attached a tar file containing them to this email.
>>
>>> I'll try this on Ubuntu myself with the version of the kernel you're using.
>>> Which version of Ubuntu is that?
>>
>> 3.13.0-53-generic
>>
>> Thanks for the help.
>
> Thanks, Martin!
>
> Argh, these don't have the debugging information and I'm not sure how to
> enable debug info for an out-of-tree module.
>
> I'll try to guess which version of Ubuntu you're using and will try it myself.
Alright, I poked around a little and the issue doesn't reproduce with the
Huion tablet I have. I found how to enable debug info for the modules you
build so the traceback can be more useful.
Could you please put this at the beginning of the makefile:
ccflags-y := -g3
recompile, reinstall the modules, plug the tablet in and send me the new
traceback from dmesg, plus hid-uclogic.* files again?
To recompile and reinstall you can use these commands:
make clean
make
sudo make install
Thank you.
Nick
|
|
From: Nikolai K. <sp...@gm...> - 2015-06-08 19:09:34
|
On 06/08/2015 08:32 AM, Martin Shepherd wrote: > Hi Nick, > > On Sun, Jun 7, 2015 at 6:31 AM, Nikolai Kondrashov <sp...@gm...> wrote: >> Can you send hid-uclogic.* files from your build? Especially hid-uclogic.o. > > I've attached a tar file containing them to this email. > >> I'll try this on Ubuntu myself with the version of the kernel you're using. >> Which version of Ubuntu is that? > > 3.13.0-53-generic > > Thanks for the help. Thanks, Martin! Argh, these don't have the debugging information and I'm not sure how to enable debug info for an out-of-tree module. I'll try to guess which version of Ubuntu you're using and will try it myself. Nick P.S. Please don't forget to keep the maillist in CC. |
|
From: Nikolai K. <sp...@gm...> - 2015-06-07 13:31:30
|
Hi Martin, On 06/01/2015 10:05 AM, Martin Shepherd wrote: > [Note that I've moved the thread from digimend-users to digimend-devel] > > Thank you for the pointer to the development version. Unfortunately > the development driver crashed when I loaded it on my system. I've > attached the corresponding traceback from dmesg. > > What I did to try the driver was as follows: I removed everything from > /lib/modules/`uname -r`/extra/, to ensure that I didn't end up running > my version of the hid_uclogic driver by mistake. I then used rmmod to > unload both usbhid and hid_uclogic. I then downloaded > https://github.com/DIGImend/digimend-kernel-drivers/archive/master.zip > and unzipped it. I ran make on this, and then sudo make install, then > verified that the new drivers appeared under /lib/modules/`uname > -r`/extra/. Finally I ran modprobe on usbhid to load it and the new > hid_uclogic driver. When the tablet didn't appear to be recognized, I > checked dmesg and found the traceback that's attached to this message. > > After that I had to reboot, because rmmod hung when I tried to unload > the crashed driver. That's a bummer. > I'll be happy to run any diagnostics that you suggest. Can you send hid-uclogic.* files from your build? Especially hid-uclogic.o. I'll try this on Ubuntu myself with the version of the kernel you're using. Which version of Ubuntu is that? Thank you. Nick |
38 messages has been excluded from this view by a project administrator.
