From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Jason Gerecke <killertofu@gmail.com>
Cc: Linux Input <linux-input@vger.kernel.org>
Subject: Re: New "ABS_WHEEL2" axis?
Date: Wed, 5 Oct 2011 20:34:52 -0700 [thread overview]
Message-ID: <201110052034.52397.dmitry.torokhov@gmail.com> (raw)
In-Reply-To: <CANRwn3SH9VO-1P_zAkDopVJRjApnZWpEZWP3YpuXg3cbiCQffg@mail.gmail.com>
On Wednesday, October 05, 2011 12:44:40 PM Jason Gerecke wrote:
> I'm working on adding support for the recently-announced Cintiq 24HD,
> and am hashing out most of the details on the linuxwacom mailing list.
> In the discussions there, it was suggested that we add a new e.g.
> "ABS_WHEEL2" axis to the input.h header to represent the second touch
> ring available on the 24HD. I think it's a good idea, but wanted to
> get some opinions from over here before making a patch. The other
> option we have available is to use an axis not already in use by the
> wacom driver (such as ABS_RUDDER), but none have a matching semantic
> meaning.
And what if next device adds another wheel? And another...
Do these rings only make sense in the context of entire Cintiq device,
or maybe they should be treated as ancillary devices (with separate
input_dev from the main tablet device)?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2011-10-06 3:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 19:44 New "ABS_WHEEL2" axis? Jason Gerecke
2011-10-06 3:34 ` Dmitry Torokhov [this message]
2011-10-06 20:31 ` Jason Gerecke
2011-11-30 22:15 ` Dmitry Torokhov
2011-11-30 22:42 ` Ping Cheng
2011-11-30 23:19 ` Dmitry Torokhov
2011-11-30 23:52 ` Jason Gerecke
2011-12-01 5:11 ` Dmitry Torokhov
2011-12-01 17:13 ` Chris Bagwell
2011-12-01 22:04 ` Jason Gerecke
2011-12-07 8:50 ` Dmitry Torokhov
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=201110052034.52397.dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=killertofu@gmail.com \
--cc=linux-input@vger.kernel.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).