From: Oliver Neukum <oneukum@suse.de>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-input@vger.kernel.org
Subject: Re: which handlers should bind to a device
Date: Fri, 11 Mar 2011 16:43:45 +0100 [thread overview]
Message-ID: <201103111643.45917.oneukum@suse.de> (raw)
In-Reply-To: <1299857944.25856.32.camel@novo.hadess.net>
Am Freitag, 11. März 2011, 16:39:02 schrieb Bastien Nocera:
> On Fri, 2011-03-11 at 16:24 +0100, Oliver Neukum wrote:
> > Hi,
> >
> > I have a set of USB speakers which also implement HID:
> <snip>
> > According to the Usage Page the device is not a keyboard, yet the keyboard handler
> > binds. Is this really sensible?
> > I: Bus=0003 Vendor=0471 Product=0104 Version=0100
> > N: Name="Philips Electronics Philips USB Digital Speaker System"
> > P: Phys=usb-0000:00:1d.0-1/input2
> > S: Sysfs=/devices/pci0000:00/0000:00:1d.0/usb6/6-1/6-1:1.2/input/input15
> > U: Uniq=
> > H: Handlers=kbd event11
> > B: PROP=0
> > B: EV=13
> > B: KEY=e000000000000 0
> > B: MSC=10
>
> As long as it's not the only thing that binds. We're just missing udev
> level information to be able to match the audio device and the sound
> device, so that pressing the buttons would change the volume on that
> device. See:
> https://bugzilla.gnome.org/show_bug.cgi?id=340720
Well then it would seem than binding to only an event interface should
make things easier for X.
Regards
Oliver
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-03-11 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 15:24 which handlers should bind to a device Oliver Neukum
2011-03-11 15:39 ` Bastien Nocera
2011-03-11 15:43 ` Oliver Neukum [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=201103111643.45917.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=hadess@hadess.net \
--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).