From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RFC] usb-wacom
Date: Thu, 14 Aug 2008 13:52:33 +0200 [thread overview]
Message-ID: <fb249edb0808140452l13a6a86fnb0b2e2604de081ba@mail.gmail.com> (raw)
In-Reply-To: <1498140435-BeMail@laptop>
Hiya,
2008/8/14 François Revol <revol@free.fr>:
> First, mouse stayed in the top-left corner... Seems coords were set to
> 0,0 when no button is pressed, which is wrong, most tablets actually
> sense the stylus even when it's not yet touching the surface.
The wacom-tablet was implemented to emulate a touchscreen originally,
because Linux doesn't by default have drivers for any hotpluggable
touchscreen. Reporting 0,0 when not touching allows the emulation to
be used with tslib. With a real tablet the stylus can also be too far
above the surface for the coords to be avilable, but I don't know what
coords are being reported then.
>
> Also, coords were wrong.
> Our driver takes the pos from the hardware, and scales them from model-
> dependant hardcoded max values:
> http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/input_server/devices/wacom/TabletDevice.cpp#L115
> down to [0.0f, 1.0f], which represents the whole screen.
> Since QEMU reports absolute mouse position scaled from screen size to
> INT16_MAX this didn't really work.
> Now, I'm not sure those max values are correct for all Penpartner
> devices, or if they were calibrated on a specific item.
I'm don't know either I'm afraid, for my use case it didn't matter
because tslib will calibrate the input anyway. It may be useful
adding the correct HID descriptors (I though we already had them).
> Best would be to actually read them from the HID descriptor, but QEMU
> doesn't provide one, and I read some penpartner tablets actually have
> wrong descriptors anyway.
>
> Finaly, I fixed button handling according to our driver, not sure all
> drivers handle them the same. pressure indicates left button, and a
> flag tells about right one. I mapped middle button to the eraser to at
> least be useful in tablet-aware software though I'm not sure it's the
> best way.
I'll check if this works with Linux also, when I get a chance. I
didn't look at your patch yet as I'm away form my desktop
Cheers
next prev parent reply other threads:[~2008-08-14 11:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 0:07 [Qemu-devel] [PATCH] [RFC] usb-wacom François Revol
2008-08-14 2:04 ` Anthony Liguori
2008-08-14 2:21 ` François Revol
2008-08-14 10:23 ` Jamie Lokier
2008-08-14 12:04 ` François Revol
2008-08-14 12:26 ` Jamie Lokier
2008-08-14 12:44 ` François Revol
2008-08-14 11:52 ` andrzej zaborowski [this message]
2008-08-14 12:17 ` François Revol
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb249edb0808140452l13a6a86fnb0b2e2604de081ba@mail.gmail.com \
--to=balrogg@gmail.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).