From: Arjan van de Ven <arjan@infradead.org>
To: Elias Naur <elias@oddlabs.com>
Cc: Dmitry Torokhov <dtor_core@ameritech.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Expose input device usages to userspace
Date: Tue, 14 Mar 2006 11:59:06 +0100 [thread overview]
Message-ID: <1142333947.3027.31.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <200603141146.04270.elias@oddlabs.com>
On Tue, 2006-03-14 at 11:46 +0100, Elias Naur wrote:
> On Tuesday 14 March 2006 09:22, Arjan van de Ven wrote:
> > > > No, I don't think this is needed at all - users should be interested in
> > > > what capabilities a particular device has, not what type it was
> > > > assigned by soneone.
> > >
> > > I see your point that an application should not rely too much on device
> > > usages. However, the main reason I want device usages is to help
> > > applications and users identify and (visually) represent devices. For
> > > example, games could show an appropriate icon graphic representing each
> > > active device. The event interface already has a few other ioctls for
> > > this kind of information:
> >
> > ok then you should consider to do it the other way around: make a way of
> > asking
> > "are you matching THIS profile".
> > rather than
> > "what profile are you"
> >
> > that way devices can present multiple faces etc; which is going to be
> > needed as more and more weird devices come into existence.
>
> If by profile you mean a device usage like Mouse, Keyboard, Joystick etc. is
> your proposal covered by the bit field ioctl exposed by my patch? For
> example, a device can already expose itself as both a joystick and a mouse
> (see the hid-input.c changes from the patch).
no that's not what I meant; I really mean asking "can you do THIS
profile". Example would be a device that could be either a joystick and
a mouse, or a touchpad and a mouse, but not both a touchpad and a
joystick. So the app should ask "can you do THESE", and the driver can
then do anything complex it wants to come to an answer. (Of course a
generic helper for the simple case is fine)
next prev parent reply other threads:[~2006-03-14 10:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 20:54 Elias Naur
2006-03-13 21:02 ` Arjan van de Ven
2006-03-14 5:26 ` Dmitry Torokhov
2006-03-14 7:21 ` Elias Naur
2006-03-14 8:22 ` Arjan van de Ven
2006-03-14 10:46 ` Elias Naur
2006-03-14 10:59 ` Arjan van de Ven [this message]
2006-03-14 11:46 ` Elias Naur
2006-03-14 5:33 ` Elias Naur
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=1142333947.3027.31.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=dtor_core@ameritech.net \
--cc=elias@oddlabs.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®