From: Mohamed Ikbel Boulabiar <medikbel@lii-enac.fr>
To: "Stéphane Chatty" <chatty@enac.fr>
Cc: Rafi Rubin <rafi@seas.upenn.edu>,
linux-input@vger.kernel.org,
Peter Hutterer <peter.hutterer@who-t.net>,
brysgo@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 14:01:09 +0200 [thread overview]
Message-ID: <45cc95260906170501u6bf26a57i9cb7b4cfc6ef49d2@mail.gmail.com> (raw)
In-Reply-To: <93BE517D-F863-4F80-8060-CC36562E02CC@enac.fr>
> 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?
This is another example raising questions about the input system, from
the kernel to Xorg to finally reach applications.
I will write another mail about this later (maybe RFC), but it seems
that some code should be modified in the kernel and input devices
should have an input daemon outside the kernel and not in X, to easily
deal with new devices and new constraints without modifying many
layers of the whole system.
(in this case, we maybe need 2 devices because the constructor
included this as a feature, but if simple users want to add some)
next prev parent reply other threads:[~2009-06-17 12:09 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 [this message]
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
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=45cc95260906170501u6bf26a57i9cb7b4cfc6ef49d2@mail.gmail.com \
--to=medikbel@lii-enac.fr \
--cc=brysgo@gmail.com \
--cc=chatty@enac.fr \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=rafi@seas.upenn.edu \
--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).