From: Jarod Wilson <jarod@redhat.com>
To: Anssi Hannula <anssi.hannula@gmail.com>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>
Subject: Re: [PATCH] hid: ignore all recent SoundGraph iMON devices
Date: Sun, 2 Aug 2009 21:16:05 -0400 [thread overview]
Message-ID: <200908022116.05450.jarod@redhat.com> (raw)
In-Reply-To: <200907311500.28866.jarod@redhat.com>
On Friday 31 July 2009 15:00:28 Jarod Wilson wrote:
> On Friday 31 July 2009 14:41:38 Anssi Hannula wrote:
> > Jarod Wilson wrote:
> > > After some inspection of the Windows iMON driver, several additional
> > > device IDs were added to the lirc_imon driver. At least a few of these
> > > have been seen in the wild, and require manual quirking to keep the
> > > usbhid driver from binding to them. Rather than list out every single
> > > device, ignore the entire device ID range, 0x0034 - 0x0046. Some of
> > > these may not advertise themselves as HID devices, but no harm done to
> > > such devices anyway. Does the right thing in brief testing w/my 0x0045
> > > device.
> >
> > I'm not sure this is a good idea. I have a 0x0038 device and I'm
> > developing a proper HID driver for it. If and when I'll submit it for
> > kernel inclusion, this kind of ID range blacklisting may get ugly.
>
> Erm, there's already a full driver for it though, and its already in
> the ignore list...
Also, out of curiosity, what does a "proper HID driver for it" look
like and/or do that the latest lirc_imon doesn't? We're already doing
input layer stuff with the mouse mode and mouse buttons, and looking to
further extend that, potentially making the driver pure input layer,
but still usable with the lirc devinput userspace driver.
--
Jarod Wilson
jarod@redhat.com
next prev parent reply other threads:[~2009-08-03 1:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 14:56 [PATCH] hid: ignore all recent SoundGraph iMON devices Jarod Wilson
2009-07-31 18:41 ` Anssi Hannula
2009-07-31 19:00 ` Jarod Wilson
2009-08-03 1:16 ` Jarod Wilson [this message]
2009-08-03 13:05 ` Anssi Hannula
2009-08-03 13:22 ` Jarod Wilson
2009-08-03 13:42 ` Anssi Hannula
2009-10-19 17:10 ` Jarod Wilson
2009-08-08 0:22 ` Jiri Kosina
2009-08-08 9:49 ` Anssi Hannula
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=200908022116.05450.jarod@redhat.com \
--to=jarod@redhat.com \
--cc=anssi.hannula@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).