From: Chris J Arges <chris.j.arges@canonical.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCH] hid: usbhid: add quirk for SB arena headset v2
Date: Mon, 05 Nov 2012 15:32:25 -0600 [thread overview]
Message-ID: <50983069.5080404@canonical.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1211052117210.24253@pobox.suse.cz>
On 11/05/2012 02:18 PM, Jiri Kosina wrote:
> On Mon, 5 Nov 2012, Chris J Arges wrote:
>
>> When an SB Arena USB headset is plugged in, it registers the volume
>> keys on the headset as a keyboard and continually sends events causing
>> issues with normal keyboard input. This quirk disables the volume keys.
>
> I don't know how the device looks like, but wouldn't it make more sense to
> actually remap the bogus keys it's sending to produce KEY_VOLUMEUP and
> KEY_VOLUMEDOWN?
>
Yes, if I can track this hardware down or get data I'll fix it like
this. This happened to be a do-no harm fix for the following bug:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1007575
Thanks for the feedback.
--chris j arges
next prev parent reply other threads:[~2012-11-05 21:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 20:05 [PATCH] hid: usbhid: add quirk for SB arena headset v2 Chris J Arges
2012-11-05 20:18 ` Jiri Kosina
2012-11-05 21:32 ` Chris J Arges [this message]
2012-11-06 11:14 ` Jiri Kosina
[not found] ` <alpine.LNX.2.00.1211061214030.24253-ztGlSCb7Y1iN3ZZ/Hiejyg@public.gmane.org>
2012-11-21 15:29 ` Chris J Arges
-- strict thread matches above, loose matches on Subject: below --
2013-01-30 1:09 Alec Warner
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=50983069.5080404@canonical.com \
--to=chris.j.arges@canonical.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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).