From: Rafi Rubin <rafi@seas.upenn.edu>
To: Jiri Kosina <jkosina@suse.cz>
Cc: "Stéphane Chatty" <chatty@enac.fr>,
jirislaby@gmail.com, "Greg KH" <greg@kroah.com>,
linux-input@vger.kernel.org
Subject: Re: IS_INPUT_APPLICATION and tablets
Date: Thu, 21 May 2009 07:28:33 -0400 [thread overview]
Message-ID: <4A153AE1.1020302@seas.upenn.edu> (raw)
In-Reply-To: <alpine.LNX.2.00.0905211105010.13917@wotan.suse.de>
Jiri Kosina wrote:
> On Thu, 21 May 2009, Rafi Rubin wrote:
>
>> Is there any downside to letting hiddev to cover all devices, even those
>> that are supported by the hid system?
>
> That's one of the possible solutions, yes. (we could either make that
> behavior configurable, with default settings to always create hiddev
> node, to preserve backwards compatibility with userspace).
>
Those codes are descriptions, not unique identifiers. It seems to me that sooner or later a conflict will arise over multiple
devices with the same code where the driver writers for devices have differing philosophies.
You could also leave a legacy version of IS_INPUT_APPLICATION with some old ranges for hiddev while letting hid-input use a version
which is free to expand. But I think forking like that would be uglier than having hiddev nodes for all devices by default.
As for a configurable solution, there's always the style used by serio_raw. Though, I think enabling hiddev shouldn't unbind the
normal hid-input driver.
Rafi
prev parent reply other threads:[~2009-05-21 11:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 21:30 IS_INPUT_APPLICATION and tablets Stéphane Chatty
2009-05-21 8:42 ` Jiri Kosina
2009-05-21 8:46 ` Rafi Rubin
2009-05-21 9:05 ` Jiri Kosina
2009-05-21 11:28 ` 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=4A153AE1.1020302@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=chatty@enac.fr \
--cc=greg@kroah.com \
--cc=jirislaby@gmail.com \
--cc=jkosina@suse.cz \
--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).