digimend-devel — Development matters

[DIGImend-devel] Tablet diagnostics

[C. F. <cfl...@gm...>]

Hi,

I just recently bought a Yiynova MSP19 which is a rebranded Waltop 
tablet, and I was wondering if I could send some diagnostics to you 
guys. Just to let you know, the tablet itself works as it should out of 
the box, but the stylus is not registering the correct input as far as 
the buttons or the pressure sensitivity goes. Would you like me to send 
it to you?

The vendor id and product id are as follows.

172f:0052.

Thanks for your help.

Flandre

Re: [DIGImend-devel] Genius PenSketch 12x9 in Ubuntu Precise (12.04)

[Favux ... <fav...@gm...>]

On Mon, Jul 23, 2012 at 11:47 PM, Viktoria S. <vik...@fr...> wrote:
> Hi!
>
> I have couple of suggestions. See bellow:
>
> "Favux ..." <fav...@gm...> írta:
>>Hi Nick,>
>>
> I have a Genius PenSketch 12x9 user on Ubuntu forums.  Originally he>
> was using Natty (11.04) and wanted to modify his tablet's aspect>
> ratio.  We figured that out.  Then he upgraded to Precise (12.04)>
> because he wanted to install the new Gimp 2.8 over the default Gimp>
> 2.6.
>
> As far as I know the default gimp in precise is 2.6, how did he installed gimp 2.8? He compiled it or installed from a custom repository? (2.8 Gimp default in Quantal 12.10 which is in alpha state.)
>
> It appears the pen may be on the third event which may be why the pen>
> isn't working in Gimp 2.8.  It still has the issue/bug Viktoria.S>
> described where it is showing one input device, namely "9x12 Tablet">
> in its Configure Extended Input Devices dropdown.  Because by happy>
> chance the pen was the first device Vicktoria.S reported things were>
> OK for drawing even so.  I can't explain how the pen event changed>
> from the first to third for the PenSketch if that is what happened.>
> Maybe the updates?>
>
> Well. I could not figured this out (I mean the device list.). I have got a "specially" compiled gimp 2.8 and on that the pen is the 2nd mousepen on the list, but if I start gimp 2.6 or mypaint the pen is the 1st mousepen on the device list (I am using 12.04 64bit digimended kernel). (Actually the pen got device id 17, and the mouse got 18......)
>
> I can suggest couple of things:
> 1. Install mypaint from the repositories. Configure the pen in mypaint and see if he can draw with the pen there. (At least in this way we can check if there is everything ok with the pen or not.)
> 2. Compile gimp 2.8 on the way I have suggested and on the device list enable only the pen.
> 3. Maybe he can try to use the wacom driver. As far as I know the wacom driver ads the word stylus to the name of the pen so in this way everything or almost everything gets a unique name. So there could not be a problem with gimp 2.8. (I am thinking about trying to use the wacom driver on 12.10 too, but only after the kernel has been update to 3.5 stable and I can configure the Oracle VM perfectly with that kernel. Later I can give feedback if I was successfull with it or not.)
>
> Good luck guys!

Thanks Viktoria S.,

We did MyPaint and his pen does work in it.

I'm pretty sure he installed from this PPA:
https://launchpad.net/~otto-kesselgulasch/+archive/gimp

So likely he (we) would need to be talked through the Gimp compile
after making the fixes you suggest in the bug report.

We could try xf86-input-wacom but that doesn't excite me at this time.
 What I would like to do is to come up with a way to differentiate the
input devices through udev so Gimp lists them all.

Favux

Re: [DIGImend-devel] Genius PenSketch 12x9 in Ubuntu Precise (12.04)

[Viktoria S. <vik...@fr...>]

Hi!

I have couple of suggestions. See bellow:

"Favux ..." <fav...@gm...> írta:
>Hi Nick,>
>
I have a Genius PenSketch 12x9 user on Ubuntu forums.  Originally he>
was using Natty (11.04) and wanted to modify his tablet's aspect>
ratio.  We figured that out.  Then he upgraded to Precise (12.04)>
because he wanted to install the new Gimp 2.8 over the default Gimp>
2.6.  

As far as I know the default gimp in precise is 2.6, how did he installed gimp 2.8? He compiled it or installed from a custom repository? (2.8 Gimp default in Quantal 12.10 which is in alpha state.)

It appears the pen may be on the third event which may be why the pen>
isn't working in Gimp 2.8.  It still has the issue/bug Viktoria.S>
described where it is showing one input device, namely "9x12 Tablet">
in its Configure Extended Input Devices dropdown.  Because by happy>
chance the pen was the first device Vicktoria.S reported things were>
OK for drawing even so.  I can't explain how the pen event changed>
from the first to third for the PenSketch if that is what happened.>
Maybe the updates?>

Well. I could not figured this out (I mean the device list.). I have got a "specially" compiled gimp 2.8 and on that the pen is the 2nd mousepen on the list, but if I start gimp 2.6 or mypaint the pen is the 1st mousepen on the device list (I am using 12.04 64bit digimended kernel). (Actually the pen got device id 17, and the mouse got 18......)

I can suggest couple of things:
1. Install mypaint from the repositories. Configure the pen in mypaint and see if he can draw with the pen there. (At least in this way we can check if there is everything ok with the pen or not.)
2. Compile gimp 2.8 on the way I have suggested and on the device list enable only the pen. 
3. Maybe he can try to use the wacom driver. As far as I know the wacom driver ads the word stylus to the name of the pen so in this way everything or almost everything gets a unique name. So there could not be a problem with gimp 2.8. (I am thinking about trying to use the wacom driver on 12.10 too, but only after the kernel has been update to 3.5 stable and I can configure the Oracle VM perfectly with that kernel. Later I can give feedback if I was successfull with it or not.)

Good luck guys!
Viktoria

[DIGImend-devel] Genius PenSketch 12x9 in Ubuntu Precise (12.04)

[Favux ... <fav...@gm...>]

Hi Nick,

I have a Genius PenSketch 12x9 user on Ubuntu forums.  Originally he
was using Natty (11.04) and wanted to modify his tablet's aspect
ratio.  We figured that out.  Then he upgraded to Precise (12.04)
because he wanted to install the new Gimp 2.8 over the default Gimp
2.6.  After he did that all was well.  Then he added the custom .conf
file to modify the aspect ratio and the tablet stopped drawing.
Removal of the custom .conf didn't fix things.  Also since installing
Gimp 2.8 was  about the first thing he did a bunch of updates for
Precise were installed, maybe at about the same time as the .conf
file.  He can't remember quite when or what they were.

Bus 003 Device 003: ID 5543:0042 UC-Logic Technology Corp. Tablet PF1209

xinput list:
⎜   ↳                 9x12 Tablet                 id=10    [slave  pointer  (2)]
⎜   ↳                 9x12 Tablet                 id=11    [slave  pointer  (2)]
⎜   ↳                 9x12 Tablet                 id=12    [slave  pointer  (2)]

In Xorg.0.log we see the the 3 event nodes.  The first and third have
the identifier "evdev tablet catchall" while the second has "evdev
pointer catchall".

Are there suppose to be two event nodes matching MatchIsTablet?

It appears the pen may be on the third event which may be why the pen
isn't working in Gimp 2.8.  It still has the issue/bug Viktoria.S
described where it is showing one input device, namely "9x12 Tablet"
in its Configure Extended Input Devices dropdown.  Because by happy
chance the pen was the first device Vicktoria.S reported things were
OK for drawing even so.  I can't explain how the pen event changed
from the first to third for the PenSketch if that is what happened.
Maybe the updates?

So <device names> that are different would be good.  I was wondering
if maybe that could be done through  udev rules.  That would be one
step up from the linux wacom X driver appending the different input
tool types but still not require kernel driver changes.  So far in
udevadm info I do not see a difference.  In other words I cannot find
whatever MatchIsTablet, MatchIsPointer, or MatchIsKeyboard is matching
to in udev.

In the PF1209's case is it the HID report descriptor's "Usage
(Stylus)" that triggers MatchIsTablet?  And "Usage (Mouse)" for
MatchIsPointer?  Do you know if that shows up in udev and if it does
how does it show up?

Favux

Re: [DIGImend-devel] Genius EasyPen M610 questions

[Lana D. <lan...@gm...>]

Bus 002 Device 003: ID 5543:000d 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          0x000d 
  bcdDevice            0.00
  iManufacturer           1 UC-LOGIC
  iProduct                2 Tablet WP1700U
  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              160mA
    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)

Re: [DIGImend-devel] Genius EasyPen M610 questions

[Nikolai K. <sp...@gm...>]

Sorry, forgot to include DIGImend-devel.

Lana, please "Reply to all" this message and send me whatever message you
get from the maillist server, if it gets rejected.

Thanks!

Sincerely,
Nick

On 07/19/2012 12:44 AM, Nikolai Kondrashov wrote:
> Hi Lana,
>
> On Wed, Jul 18, 2012 at 9:10 AM, Lana Druzetich
> <lan...@gm...>  wrote:
>> Hello. I did another pen coordinates dump, and, strangely, my tablet stopped
>> responding afterwards.
>
> First of all, thanks for the dumps! What part of the system stopped
> responding to the tablet input? Do you get anything from dumping?
>
>> Since the last time we spoke, I switched to 64 bit Windows 7, and 64 bit
>> Ubuntu, and one of the problems I had before is gone now (the tablet is
>> always recognized as a tablet, never as a mouse), except when I unplug it
>> live, and then plug it back in (I have to restart my PC to get it working
>> again, but now restarting fixes it every time). The tablet is, however, is
>> still heavily miscalibrated at first, and I have to enter some unusual
>> values to get the whole surface area working (40000 0 42000 20000). I'm
>> pretty sure I damaged the tablet's firmware, back when I used Ubuntu 10, and
>> wizardpen, since Windows (XP, 7 x86, and 7 x64) wouldn't recognize it since
>> then, that is, they do recognize it, but as a USB composite device, not by
>> it's id (PW1700U). Another gem is the fact that when i install drivers from
>> Windows update, the tablet works, but I get the same miscalibration I get in
>> Ubuntu at start, and I can not fix it in Windows. For comparison purposes,
>> when I plugged in a similar tablet (WP5540U, I never used this one on
>> Ubuntu, if that means anything) it was instantly recognized in both Windows
>> (by it's name, and as a single USB device) and Ubuntu (hotplugging worked
>> just fine), and it required no calibration in either system.
>>
>> I hope this clears things up a bit.
>
> Thanks for the description! I've implemented WP5540U driver quite a long
> time ago and it is a very simple and straight-forward device, although, as
> usual, not standard compliant.
>
> I doubt that you damaged the firmware, there is usually no way to do that.
> However, it could have been quirky to start with.
>
> I think this mouse/tablet flipping is due to switching of the tablet modes.
> I have a suspicion that the firmware designers used some strange way of
> triggering it and it is getting switched accidentally by some sequence of
> events on the USB bus.
>
> Now, if we won't find this sequence, there is a high possibility we can work
> around this random switching in the kernel driver.
>
> The modes differ slightly by the report IDs and format. I have full report
> format for the default mode sent by you previously, and pen coordinates for
> the proprietary mode. Can you please do pen buttons and frame buttons dump
> for the proprietary mode?
>
> You can see which mode your tablet is in by starting a dump and seeing which
> report ID is used to report pen movement. If the first byte of each report
> is 09 - it is the default mode, if it is 07 - it is the proprietary mode.
>
> This is an example of default mode reports:
>
> 002:002:000:STREAM             1341769148.182056
>   09 80 F0 57 E6 A4 00 00
>
> 002:002:000:STREAM             1341769148.186029
>   09 80 F0 57 E6 A4 00 00
>
> 002:002:000:STREAM             1341769148.190024
>   09 80 F0 57 E6 A4 00 00
>
> These are proprietary mode reports:
>
> 002:003:000:STREAM             1342590809.450792
>   07 C0 7E A0 22 77 00 00
>
> 002:003:000:STREAM             1342590809.462649
>   07 C0 2F A0 22 77 00 00
>
> 002:003:000:STREAM             1342590809.470647
>   07 C0 D0 9F 22 77 00 00
>
> I need pen buttons and frame buttons dumps for the second (proprietary)
> mode. However, if it refuses to switch to it again, I can do a good guess as
> to how it would work and do without the dump.
>
> Thank you!
>
> Sincerely,
> Nick
>
> P.S. Could you please "Reply to all" this message and send me whatever error
> message you get back from the maillist server, if it gets rejected?

[DIGImend-devel] Genius EasyPen M610 questions

[Nikolai K. <sp...@gm...>]

Hi Lana,

Thanks for the dumps! I've taken a look at them and the coordinate reporting
and the pen report descriptor surely look strange.

The coordinate ranges don't constitute a round number or close to it, which
is unusual and suspicious. Could you please repeat pen coordinate dump?

This time, please slowly move your pen horizontally, from out the left side
of the working area, through the middle, and out on the right side. Then do
this vertically, starting from the top. Please ensure that the pen both
starts and stops outside the working area. It doesn't have to be a very
straight line.

First like this:

      `:
     .-~---------------------------.
     |    * * * *                  |
     |  .-----------------------.  |
     |  |                       |  |
     |  |                       |  |
     | --------------------------> |
     |  |                       |  |
     |  |                       |  |
     |  |                       |  |
     |  `-----------------------'  |
     |                             |
     `-----------------------------'

Then like this:

      `:
     .-~---------------------------.
     |    * * * *   |              |
     |  .---------- | ----------.  |
     |  |           |           |  |
     |  |           |           |  |
     |  |           |           |  |
     |  |           |           |  |
     |  |           |           |  |
     |  |           |           |  |
     |  `---------- | ----------'  |
     |             \|/             |
     `-----------------------------'

Please repeat this three times and send me the resulting file.

Have you figured out any pattern behind "spontaneous" mouse/tablet switching
Dave has described?

Will you be able to test a kernel package? Which distribution release do you
use, is it 32 or 64 bits?

Thank you!

Sincerely,
Nick

Re: [DIGImend-devel] Some problems with hidrd-convert

[Nikolai K. <sp...@gm...>]

On 07/15/2012 11:11 AM, Mitch Davis wrote:
> On Sun, Jul 8, 2012 at 6:21 PM, Nikolai Kondrashov<sp...@gm...>  wrote:
>>
>> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/generic-usb/unbind
>> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/waltop/bind
>>
>> The format of HID bus device ID is this:
>>
>> TRANSPORT_BUS_ID:VENDOR_ID:PRODUCT_ID.DEVICE_NUMBER
>
> Very strange, the numbers I need are not what I expect:

The device number in the HID bus device ID is *not* USB bus device number.
It's a number local to the HID bus - just an ordinal number of a connected
device. HID is a high-level bus and uses other buses for transport.
Currently USB and Bluetooth are supported. The first number in the HID
device ID is the transport bus ID, 3 being USB.

> Also, I'm having a problem with loading modules:
>
>    https://bugzilla.redhat.com/show_bug.cgi?id=840267
>
> I think I'll have to wait for a solution to that before proceeding.

You can build your own kernel and work in-tree in the meantime.

>> You can copy the approach used in drivers/hid/hid-uclogic.c - it is
>> hard to do simpler. I can help you with making a report descriptor, if
>> needed.
>
> Yes I'd like your help please?  Do you understand the format of the
> current report?

I assume that you mean format of the reports. You described it quite well -
I guess I will be able to understand it.

However, you haven't told me how you want this tablet/touchpad to be
represented and whether you want to submit the driver upstream or not.
Without this I can't make a meaningful report descriptor.

Sincerely,
Nick

Re: [DIGImend-devel] Some problems with hidrd-convert

[Mitch D. <mjd...@af...>]

On Sun, Jul 8, 2012 at 6:21 PM, Nikolai Kondrashov <sp...@gm...> wrote:
>
> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/generic-usb/unbind
> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/waltop/bind
>
> The format of HID bus device ID is this:
>
> TRANSPORT_BUS_ID:VENDOR_ID:PRODUCT_ID.DEVICE_NUMBER

Very strange, the numbers I need are not what I expect:

[root@xiaomao /]# cd /sys/bus/hid/drivers/hid-generic/
[root@xiaomao hid-generic]# ls -la
total 0
drwxr-xr-x.  2 root root    0 Jul 14 18:37 .
drwxr-xr-x. 15 root root    0 Jul 14 18:37 ..
lrwxrwxrwx.  1 root root    0 Jul 14 19:20 0003:040B:2013.0001 ->
../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:040B:2013.0001
lrwxrwxrwx.  1 root root    0 Jul 14 19:20 0003:040B:2013.0002 ->
../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:040B:2013.0002
lrwxrwxrwx.  1 root root    0 Jul 14 19:20 0003:08F2:6370.0003 ->
../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3/2-1.3:1.0/0003:08F2:6370.0003
--w-------.  1 root root 4096 Jul 14 18:37 bind
--w-------.  1 root root 4096 Jul 14 18:37 new_id
--w-------.  1 root root 4096 Jul 14 18:37 uevent
--w-------.  1 root root 4096 Jul 14 18:37 unbind
[root@xiaomao hid-generic]# lsusb
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0402:9665 ALi Corp.
Bus 002 Device 003: ID 040b:2013 Weltrend Semiconductor
Bus 002 Device 004: ID 08f2:6370 Gotop Information Inc.

## Note the bus and device number.  I'll try according to your formula:

[root@xiaomao hid-generic]# echo 0002:08f2:6370:0004 > unbind
bash: echo: write error: No such device

## Let's try the symlink from the dir listing:

[root@xiaomao hid-generic]# echo 0003:08F2:6370.0003 > unbind

## No error message!

[root@xiaomao hid-generic]# ls -la
total 0
drwxr-xr-x.  2 root root    0 Jul 14 18:37 .
drwxr-xr-x. 15 root root    0 Jul 14 18:37 ..
lrwxrwxrwx.  1 root root    0 Jul 14 19:20 0003:040B:2013.0001 ->
../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:040B:2013.0001
lrwxrwxrwx.  1 root root    0 Jul 14 19:20 0003:040B:2013.0002 ->
../../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/0003:040B:2013.0002
--w-------.  1 root root 4096 Jul 14 18:37 bind
--w-------.  1 root root 4096 Jul 14 18:37 new_id
--w-------.  1 root root 4096 Jul 14 18:37 uevent
--w-------.  1 root root 4096 Jul 14 19:22 unbind
[root@xiaomao hid-generic]#

Also, I'm having a problem with loading modules:

  https://bugzilla.redhat.com/show_bug.cgi?id=840267

I think I'll have to wait for a solution to that before proceeding.

> You can copy the approach used in drivers/hid/hid-uclogic.c - it is
> hard to do simpler. I can help you with making a report descriptor, if
> needed.

Yes I'd like your help please?  Do you understand the format of the
current report?

Mitch.

Re: [DIGImend-devel] Some problems with hidrd-convert

[Nikolai K. <sp...@gm...>]

Hi Mitch,

On 07/14/2012 08:26 AM, Mitch Davis wrote:
>> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/generic-usb/unbind
>
> Newb question, but I can't find that virtual file, only
> /sys/bus/hid/drivers/hid-generic/unbind.  Is it the same thing, or
> something different?  If it's different, how do I get that one?  Which
> module should I load to make it appear?

It appears the 3.5 kernel changed it and "hid-generic" is the new driver.
So, use it instead of "generic-usb".

> Also, regarding the four numbers, in particular the fourth number.  In
> your example, it's 0002.  On my machine, if I do lsusb, the tablet is
> on bus 2, device 41.  Will this do the job?
>
> echo 0002:08F2:6370:0029>  unbind

Sure. Every HID device plugged in gets a new fourth number. So if you just
unplug and plug back the same device it will get assigned the next number.

BTW, I failed to reproduce the hidrd-convert problem on a freshly installed
Fedora 16 64 bits so far.

Sincerely,
Nick

Re: [DIGImend-devel] Some problems with hidrd-convert

[Mitch D. <mjd...@af...>]

On Sun, Jul 8, 2012 at 6:21 PM, Nikolai Kondrashov <sp...@gm...> wrote:
> Hi Mitch,
>
> echo 0003:172F:0502.0002 | sudo tee /sys/bus/hid/drivers/generic-usb/unbind

Newb question, but I can't find that virtual file, only
/sys/bus/hid/drivers/hid-generic/unbind.  Is it the same thing, or
something different?  If it's different, how do I get that one?  Which
module should I load to make it appear?

Also, regarding the four numbers, in particular the fourth number.  In
your example, it's 0002.  On my machine, if I do lsusb, the tablet is
on bus 2, device 41.  Will this do the job?

echo 0002:08F2:6370:0029 > unbind

Thanks,

Mitch.

Re: [DIGImend-devel] Genius EasyPen M610

[Nikolai K. <sp...@gm...>]

Hi Dave,

On 07/10/2012 06:22 PM, Favux ... wrote:
>> Yes, it is easy to make a userspace utility using libusb, or, probably,
>> hidapi. However, see below.
>
> I'm interested in something like that.

Can you please submit a bug for this, so it is not lost? I'll try to find
some time to implement it.

>> Um, which coordinate inversion problem? Could you please CC your replies to
>> Lana to DIGImend-devel, even though she can't send her messages there?
>
> The discussion is a continuation of the Ubuntu forms thread LannaD
> started.  Not e-mail correspondence.

Ah, OK. I've found the thread now. Will take a look.

>> I doubt that Windows could affect that. The devices are supposed to be reset
>> on reboot, I think. However, this behavior is indeed strange. X.org logs for
>> both cases would help to understand the issue.
>
> Right but when LannaD installed some tablet drivers in Windows and
> then rebooted to Ubuntu the tablet was magically recognized as a
> tablet.  LannaD has been looking at the Xorg.0.logs but I don't know
> if copies of all of them have been preserved.  I have one or two
> partials.  We're usually seeing a mouse with relative axes and
> occasionally a tablet with absolute axes.

I'm still unsure how this could happen unless device somehow changes the
report descriptor, or there is a bug somewhere in the kernel or X.org.

> I'm reasoning by analogy from toggling the KYE to get tablet reporting
> and other examples.  For instance the Wacom Graphire bluetooth starts
> defaulted to low speed bluetooth.  And low speed only reports mouse
> data.  The bluetooth has to be toggled to go into high speed protocol
> mode so it will report the tablet data.

UC-Logic has configuration commands for their tablets too. It's just I
haven't seen any of their tablets requiring it for pen input. I've seen some
frame button configuration happening, but not pen.

>> I don't think that it would help much without the kernel changes. My guess
>> is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in
>> drivers/hid/usbhid/hid-quirks.c.
>
> Earlier LannaD had the tablet "working" before several reinstalls of
> different Ubuntu releases.  An attempt to use the WizardPen driver in
> Lucid was made.  Now we're back in Precise and I did manage to compile
> the WizardPen driver in Precise.  Again looking for a stop gap
> alternative until there was a kernel driver.

The WizardPen driver may help, judging from the report descriptor. However,
this mouse/tablet switching might affect it.

To me this model feels to be somewhere in the middle between the classical
(WP8060U, WP5540U, etc) and some of the latest models (TWHL850).

>> Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think
>> the KYE tablet-enabling routine would help. But it maybe worth a try.
>
> Well you did say it was an earlier version of a current KYE, KYE made,
> tablet.  So I was hoping.

I doubt it. The report IDs are different, this tablet has two interfaces,
but KYE tablets always have one.

> Basically I'm just wondering if it would be possible to give users a
> temporary work around so they can at least use their tablets to draw.
> LannaD's is not the first time I've seen someone claim to have a
> non-supported tablet kind of working.  Since the tablet buttons won't
> work and maybe even the stylus buttons I don't think a stop gap
> solution like that would decrease the likely hood of folks sending in
> tablet diagnostics to get a true kernel driver.

I'm all for it. It's just finding and maintaining such solutions requires a
lot more time, so I can't afford it.

> But if the kernel won't permit it and instead blocks it oh well.  I
> would like an alternative to instructing folks to work with the
> kernel.  I just don't think we'll ever get that many digital artists
> enthusiastic about doing that.

In this case, the WizardPen driver will very likely work.

Linux and Windows took opposite design decisions for handling multiple
report IDs, it seems. I think Windows, basically, routes them to separate
input devices and Linux, by default, to a single device. Some devices might
have worked better out of the box in Linux if not for this (including this
tablet), but I'm not sure about the whole picture.

Sincerely,
Nick

Re: [DIGImend-devel] Genius EasyPen M610

[Favux ... <fav...@gm...>]

On Tue, Jul 10, 2012 at 3:36 AM, Nikolai Kondrashov <sp...@gm...> wrote:
> Hi Dave,
>
> Yes, it is easy to make a userspace utility using libusb, or, probably,
> hidapi. However, see below.

I'm interested in something like that.

> Um, which coordinate inversion problem? Could you please CC your replies to
> Lana to DIGImend-devel, even though she can't send her messages there?

The discussion is a continuation of the Ubuntu forms thread LannaD
started.  Not e-mail correspondence.

> I doubt that Windows could affect that. The devices are supposed to be reset
> on reboot, I think. However, this behavior is indeed strange. X.org logs for
> both cases would help to understand the issue.

Right but when LannaD installed some tablet drivers in Windows and
then rebooted to Ubuntu the tablet was magically recognized as a
tablet.  LannaD has been looking at the Xorg.0.logs but I don't know
if copies of all of them have been preserved.  I have one or two
partials.  We're usually seeing a mouse with relative axes and
occasionally a tablet with absolute axes.

I'm reasoning by analogy from toggling the KYE to get tablet reporting
and other examples.  For instance the Wacom Graphire bluetooth starts
defaulted to low speed bluetooth.  And low speed only reports mouse
data.  The bluetooth has to be toggled to go into high speed protocol
mode so it will report the tablet data.

> I don't think that it would help much without the kernel changes. My guess
> is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in
> drivers/hid/usbhid/hid-quirks.c.

Earlier LannaD had the tablet "working" before several reinstalls of
different Ubuntu releases.  An attempt to use the WizardPen driver in
Lucid was made.  Now we're back in Precise and I did manage to compile
the WizardPen driver in Precise.  Again looking for a stop gap
alternative until there was a kernel driver.

We've been trying to replicate that former "working" state on the thread.

> Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think
> the KYE tablet-enabling routine would help. But it maybe worth a try.

Well you did say it was an earlier version of a current KYE, KYE made,
tablet.  So I was hoping.

> Unfortunately, I lost the ability to have an external IP for my home server,
> so I can't give you a tarball link to the KYE-tailored usbhid-dump, but you
> can checkout "kye" branch of
> git://digimend.git.sourceforge.net/gitroot/digimend/usbhid-dump.git and run
> "./bootstrap && ./configure && make dist" to produce one.

Thanks, I'll check it out.

Basically I'm just wondering if it would be possible to give users a
temporary work around so they can at least use their tablets to draw.
LannaD's is not the first time I've seen someone claim to have a
non-supported tablet kind of working.  Since the tablet buttons won't
work and maybe even the stylus buttons I don't think a stop gap
solution like that would decrease the likely hood of folks sending in
tablet diagnostics to get a true kernel driver.

But if the kernel won't permit it and instead blocks it oh well.  I
would like an alternative to instructing folks to work with the
kernel.  I just don't think we'll ever get that many digital artists
enthusiastic about doing that.

Favux

Re: [DIGImend-devel] Genius EasyPen M610

[Favux ... <fav...@gm...>]

On Tue, Jul 10, 2012 at 3:18 AM, Viktoria S. <vik...@fr...> wrote:
> Hi!
>
> When Nick was working on the Genius Mousepen i608X driver he sent me a modified usbhid-dump, which was succesfully turned the tablet into tablet mode. After that I could get pressure from the pen. So maybe it is possible to write a little program which turns on the tablet, but I don't remember how the mouse worked in that case. If I got time I can run a little test with that modified usbhid-dump, to see how it is working.

That would be great Viktoria S.  I'd really appreciate that.

Although as Nick points out it is a UC-Logic tablet I'm hoping things
are similar enough that the same or very similar method would work for
LannaD's tablet.

Favux

Re: [DIGImend-devel] Genius EasyPen M610

[Nikolai K. <sp...@gm...>]

Hi Dave,

On Tue, Jul 10, 2012 at 9:37 AM, Favux ... <fav...@gm...> wrote:
> I was wondering if there was any chance the method you discovered with
> Viktoria of "turning on" the new KYE tablets data reporting could be
> done from user space?  Is there some way to toggle the usb protocol
> without having to do it in the kernel?  I'm assuming it is the
> tablet's firmware we need to toggle.

Yes, it is easy to make a userspace utility using libusb, or, probably,
hidapi. However, see below.

> We seem to have LanaD's M610 coordinate and axes inversion problem
> licked with the appropriate 52-evdev.conf.

Um, which coordinate inversion problem? Could you please CC your replies to
Lana to DIGImend-devel, even though she can't send her messages there?

> But evdev usually treats the tablet as a mouse only occasionally handling
> it as a tablet.  Maybe when restarting from Windows?

I doubt that Windows could affect that. The devices are supposed to be reset
on reboot, I think. However, this behavior is indeed strange. X.org logs for
both cases would help to understand the issue.

> Being able to do that would let KYE users get some functionality out of
> their "new" tablets while waiting for the kernel driver's to be made.

I don't think that it would help much without the kernel changes. My guess
is that the tablets would at least need a HID_QUIRK_MULTI_INPUT in
drivers/hid/usbhid/hid-quirks.c.

Still, M610 is not a KYE tablet. It's UC-Logic tablet. So, I don't think
the KYE tablet-enabling routine would help. But it maybe worth a try.

Unfortunately, I lost the ability to have an external IP for my home server,
so I can't give you a tarball link to the KYE-tailored usbhid-dump, but you
can checkout "kye" branch of
git://digimend.git.sourceforge.net/gitroot/digimend/usbhid-dump.git and run
"./bootstrap && ./configure && make dist" to produce one.

Sincerely,
Nick

Re: [DIGImend-devel] Genius EasyPen M610

[Viktoria S. <vik...@fr...>]

Hi!

When Nick was working on the Genius Mousepen i608X driver he sent me a modified usbhid-dump, which was succesfully turned the tablet into tablet mode. After that I could get pressure from the pen. So maybe it is possible to write a little program which turns on the tablet, but I don't remember how the mouse worked in that case. If I got time I can run a little test with that modified usbhid-dump, to see how it is working.

Kind regards:
Viktoria

"Favux ..." <fav...@gm...> írta:
>Hi Nick,>
>
Forgive me if this is a silly question.>
>
I was wondering if there was any chance the method you discovered with>
Viktoria of "turning on" the new KYE tablets data reporting could be>
done from user space?  Is there some way to toggle the usb protocol>
without having to do it in the kernel?  I'm assuming it is the>
tablet's firmware we need to toggle.>
>
We seem to have LanaD's M610 coordinate and axes inversion problem>
licked with the appropriate 52-evdev.conf.  But evdev usually treats>
the tablet as a mouse only occasionally handling it as a tablet.>
Maybe when restarting from Windows?>
>
Being able to do that would let KYE users get some functionality out>
of their "new" tablets while waiting for the kernel driver's to be>
made.>
>
Favux>
>
------------------------------------------------------------------------------>
Live Security Virtual Conference>
Exclusive live event will cover all the ways today's security and >
threat landscape has changed and how IT managers can respond. Discussions >
will include endpoint security, mobile security and the latest in malware >
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/>
_______________________________________________>
DIGImend-devel mailing list>
DIG...@li...>
https://lists.sourceforge.net/lists/listinfo/digimend-devel>

Re: [DIGImend-devel] Genius EasyPen M610

[Favux ... <fav...@gm...>]

Hi Nick,

Forgive me if this is a silly question.

I was wondering if there was any chance the method you discovered with
Viktoria of "turning on" the new KYE tablets data reporting could be
done from user space?  Is there some way to toggle the usb protocol
without having to do it in the kernel?  I'm assuming it is the
tablet's firmware we need to toggle.

We seem to have LanaD's M610 coordinate and axes inversion problem
licked with the appropriate 52-evdev.conf.  But evdev usually treats
the tablet as a mouse only occasionally handling it as a tablet.
Maybe when restarting from Windows?

Being able to do that would let KYE users get some functionality out
of their "new" tablets while waiting for the kernel driver's to be
made.

Favux

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Favux ... <fav...@gm...>]

On Mon, Jul 9, 2012 at 10:56 AM, Nikolai Kondrashov <sp...@gm...> wrote:
>
> BTW, SourceForge.net has sent a new mail today improving and
> clarifying the migration plan slightly.

Nick could you forward me a copy of that?  Peter went on vacation
today so I don't know if he'll get around to forwarding that to me,
not for a while at least.

Thanks,

Dave

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Nikolai K. <sp...@gm...>]

On Mon, Jul 9, 2012 at 6:39 PM, Favux ... <fav...@gm...> wrote:
> I really don't want to throw away the nice templates you two have
> made.  Coding replacements may turn out to be a time consumer.

Yes, me neither. However, I'm a little worried about the direction
SourceForge.net is heading. Wordpress was broken for several months
without any word about when it would work again and then an
announcement to discontinue it. The project statistics were also
broken several times for quite long periods before.

> Peter points out the using 1.16.5 should be OK.  He has a point given
> the issue they have their hosted app is probably at most in the 1.16.x
> series so if we use 1.16.5 we shouldn't run into any
> incompatibilities.  He also isn't conerned about upgrading the
> MediaWiki, thinks it is just a matter of downloading and unzipping the
> tarball.

Hopefully it will be so.

> I don't know about the maintenance issues.  But it seems to
> me they're present in any wiki.

It's just that before I didn't have to fix it in case it broke and now
I'll be responsible for it and for tracking the security updates also.

> So one of the two main hurdles disposed of anyway.
>
> We're going to try and migrate the Linux Wacom Project's MediaWiki on
> Tuesday August 14.  So I should be able to let you know how that went
> afterwards.

Thank you :)

BTW, SourceForge.net has sent a new mail today improving and
clarifying the migration plan slightly.

Sincerely,
Nick

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Favux ... <fav...@gm...>]

I really don't want to throw away the nice templates you two have
made.  Coding replacements may turn out to be a time consumer.

Peter points out the using 1.16.5 should be OK.  He has a point given
the issue they have their hosted app is probably at most in the 1.16.x
series so if we use 1.16.5 we shouldn't run into any
incompatibilities.  He also isn't conerned about upgrading the
MediaWiki, thinks it is just a matter of downloading and unzipping the
tarball.  I don't know about the maintenance issues.  But it seems to
me they're present in any wiki.

So one of the two main hurdles disposed of anyway.

We're going to try and migrate the Linux Wacom Project's MediaWiki on
Tuesday August 14.  So I should be able to let you know how that went
afterwards.

Dave

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Nikolai K. <sp...@gm...>]

Hi Viktoria,

On Mon, Jul 9, 2012 at 6:22 PM, Viktoria S. <vik...@fr...> wrote:
> I hope you had a great vacation :)!

Thanks :) It was only a sort-of vacation, because I still worked on my day
job most of the time. But it was fine for what it was :)

> I found a great comparison of software hosting sites here:
> http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities
>
> At https://github.com/ here: https://github.com/features/projects/wikis
> they are mentioning that they are even providing git powered wikis. And it's free for open source projects.
>
> And maybe it worth to look at https://gitorious.org/ too. This site hosts
> qt, and it has a wiki too, you can take a look at that here:
> https://qt.gitorious.org/qt/pages/Home. I think that look all right and it
> seems it is git based too. (You can git clone the wiki if you want to.)

Thanks, I've already looked through these pages. I really like the idea of
git-based wiki's or any file and source control-based wiki for that matter.
However, I didn't find any which would support templates. Maybe I'll invent
some replacement for them.

Sincerely,
Nick

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Viktoria S. <vik...@fr...>]

Hi Nick,

I hope you had a great vacation :)!
I found a great comparison of software hosting sites here:
http://en.wikipedia.org/wiki/Comparison_of_open_source_software_hosting_facilities

At https://github.com/ here: https://github.com/features/projects/wikis
they are mentioning that they are even providing git powered wikis. And it's free for open source projects.

And maybe it worth to look at https://gitorious.org/ too. This site hosts qt, and it has a wiki too, you can take a look at that here: https://qt.gitorious.org/qt/pages/Home. I think that look all right and it seems it is git based too. (You can git clone the wiki if you want to.)

Kind regards:
Viktoria

Nikolai Kondrashov <sp...@gm...> írta:
>
And I'm really starting to think about changing the platform completely.>
>
What do you think? Do you have any ideas where we should move our stuff and>
how much of it?>
>
Sincerely,>
Nick>

Re: [DIGImend-devel] SourceForge retiring hosted apps

[Nikolai K. <sp...@gm...>]

Hi Dave, Viktoria,

On Mon, Jul 9, 2012 at 12:18 AM, Favux ... <fav...@gm...> wrote:
> I don't know if Nick has had a chance to look at the SourceForge
> e-mail notice yet or not.

Yes, I've seen it.

> They're dropping the hosted MediaWiki like they have Wordpress.  So now we
> have to set up our own MediaWiki by September along with Wordpress for the
> blog.  This stinks especially because we just finished getting the wiki
> up.
>
> Currently there is a major gotcha.  You'd want to install the current
> mediawiki-1.19.1 version but right now it doesn't work on SourceForge.
>  Neither does version 1.18 or 1.17.  Apparently you have to go back to
> version 1.16.5.  They make no guarantee they'll have SourceForge
> compatible with MediaWiki's current version when they sunset the
> hosted MediaWiki in September.  In fact they provide themselves an out
> by referring us to a third party MediaWiki hosting site like:
> http://wikkii.com/wiki/Free_Wiki_Hosting  So their migration sites
> need to be monitored for an announcement that they've fixed the issue.
>  Hopefully it isn't so late in the game that it turns into a mad
> scramble.
>
> Also they'll have to implement OpenID authentication to SourceForge
> accounts.  So watch out for that announcement too.  Probably want SF
> URL Shortener and Redirects from old Hosted App locations, also not
> implemented but likely of lesser importance.  I'm not sure what
> they're talking about with their new Allura platform.  What it buys
> you migrating to that.  Some claim about easier data migration because
> of a new data API?  We're a Classic project, correct?

Yes, we're a Classic project.

> Once past those hurdles the tricky part appears to be the MediaWiki
> LocalSettings.php configuration script.  It's needed because the
> MediaWiki's installer thinks it is dealing with a fresh install.  So
> you have to include a LocalSettings.php file in the base of your
> MediaWiki install.  Get that wrong and I suppose you have to reinstall
> and reload from your data backup.
>
> The main issue though is that the migration has to be done by someone
> with administrator privileges.  So I think you're stuck with it Nick.
> Sorry.

Thanks for a detailed explanation of the issues, Dave.

SourceForge.net was showing signs of maintenance deprivation for a while.
Their staff seems to be stretched. I really wouldn't like to maintain my own
install of MediaWiki and, say, Wordpress. I'd rather spend my time on direct
project tasks.

Considering all of the above, I think it would be a safer bet to just move
the Wiki off SourceForge.net. And the blog too.

And I'm really starting to think about changing the platform completely.

What do you think? Do you have any ideas where we should move our stuff and
how much of it?

Sincerely,
Nick

Re: [DIGImend-devel] Genius EasyPen M610

[Nikolai K. <sp...@gm...>]

Hi Dave,

On Mon, Jul 9, 2012 at 9:38 AM, Favux ... <fav...@gm...> wrote:
> I'm sending this for LannaD because she's having touble e-mailing the
> devel list for some reason.  She has what I think is a new model to us
> bought about a year ago.
>
> Genius EasyPen M610/ 6x10 Tablet/ UC-LOGIC Tablet WP1700U
>
> The tablet diagnostics are attached.

Thanks, Dave. I too received a message from her and I'm puzzled about the
reason of the failures she encountered.

I think this tablet is the previous version of M610X, produced before KYE
started designing their own tablets.

I'll take a look at the dump soon.

Sincerely,
Nick

Re: [DIGImend-devel] digimend

[Nikolai K. <sp...@gm...>]

Hi Lana,

On Sun, Jul 8, 2012 at 10:49 PM, Lana Druzetich
<lan...@gm...> wrote:
> Hello, sorry to bother on this e-mail address,

Sure, it's not a problem. We ask to send such messages to the maillist just
so others could see them.

> but I tried to send Genius EasyPen 610 raw data to
> DIG...@li... six times so far, and I kept getting
> this error: "550 550 unknown user (state 13)", and my mails kept being
> rejected.

This is strange. I suspect breakage on sourceforge.net part. We didn't have
any problem receiving messages from gmail.com before.

> is there another way to send the data to you, other than through your
> private e-mail address?

I don't think other ways are necessary. It's perfectly OK to use this
address.

Dave "Favux" has since forwarded your message to digimend-devel and I'll
look through the data soon.

Thank you!

Sincerely,
Nick