From: Rafi Rubin <rafi@seas.upenn.edu>
To: "Stéphane Chatty" <chatty@enac.fr>
Cc: linux-input@vger.kernel.org,
Peter Hutterer <peter.hutterer@who-t.net>,
brysgo@gmail.com, Mohamed Ikbel Boulabiar <boulabiar@gmail.com>,
Sebastien Hamdani <sebastien.hamdani@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>
Subject: Re: [PATCH] Restoring usages used by the pen.
Date: Wed, 17 Jun 2009 16:47:53 -0400 [thread overview]
Message-ID: <4A395679.1070607@seas.upenn.edu> (raw)
In-Reply-To: <93BE517D-F863-4F80-8060-CC36562E02CC@enac.fr>
> TBH, this is not a big loss to me personally, because:
> - so far I had not been able to give the appropriate Xmax and Ymax
> parameters to the Wacom Xorg driver, so the pointer was badly warped and
> this was pretty useless anyway.
Certainly early on, I was not able to get the wacom to accept the the ranges for the touch device, so I just put the values in my
xorg.conf and have not looked back. I think the limitation was in the userspace driver, not the device or kernel space. It was
getting the correct parameters for the pen input device.
> I guess the whole issue is to try and understand what will be the most
> popular uses of this device:
> - with which version of the firmware? the one with stylus and single
> touch? the one with multitouch but no stylus?
> - as a touch screen? as a pen computer?
It would be really nice if we could get ntrig to weigh in on the firmwares. At this point we have no way to know what the real
limitations are. It would be really nice of them to provide a firmware that gives maximal functionality. Perhaps they ran into
some design flaws which they are still trying to work around.
Anyone out there have any experience extracting firmware from windows drivers? And if we do get the raw firmware, how do we load it?
> Leaving aside the pain of having incompatible versions of the firmware
> around, it looks this type of dual device (stylus + finger) challenges
> the way linux-hid, linux-input and Xorg regard touch devices: yes,
> something that looks like a touchscreen can be a digitizer too... Maybe
> we should create two Linux devices, one for the stylus and one for fingers?
On the surface, I like the idea of separate devices. But if we still have to deal with the different fingers in user space, does it
make more sense to just use the same code to differentiate the pen?
prev parent reply other threads:[~2009-06-17 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 2:39 [PATCH] Restoring usages used by the pen Rafi Rubin
2009-06-17 9:23 ` Stéphane Chatty
2009-06-17 12:01 ` Mohamed Ikbel Boulabiar
2009-06-17 18:34 ` Rafi Rubin
2009-06-17 19:29 ` Stéphane Chatty
2009-06-17 20:35 ` Rafi Rubin
2009-06-17 20:47 ` Rafi Rubin [this message]
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=4A395679.1070607@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=boulabiar@gmail.com \
--cc=brysgo@gmail.com \
--cc=chatty@enac.fr \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rydberg@euromail.se \
--cc=sebastien.hamdani@gmail.com \
/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).