From: Bastien Nocera <hadess@hadess.net>
To: Tino Keitel <tino.keitel@tikei.de>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Matthew Garrett <mjg@redhat.com>,
Tino Keitel <tino.keitel@gmx.de>
Subject: Re: [PATCHes] Apple IR receiver driver
Date: Mon, 18 Jan 2010 14:51:11 +0000 [thread overview]
Message-ID: <1263826271.20565.2769.camel@localhost.localdomain> (raw)
In-Reply-To: <20100118143412.GA9831@mac.home>
On Mon, 2010-01-18 at 15:34 +0100, Tino Keitel wrote:
> On Mon, Jan 18, 2010 at 14:14:25 +0000, Bastien Nocera wrote:
>
> [...]
>
> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -1540,6 +1540,8 @@ static const struct hid_device_id hid_ignore_list[] = {
> > { HID_USB_DEVICE(USB_VENDOR_ID_AIPTEK, USB_DEVICE_ID_AIPTEK_24) },
> > { HID_USB_DEVICE(USB_VENDOR_ID_AIRCABLE, USB_DEVICE_ID_AIRCABLE1) },
> > { HID_USB_DEVICE(USB_VENDOR_ID_ALCOR, USB_DEVICE_ID_ALCOR_USBRS232) },
> > + { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IRCONTROL) },
> > + { HID_USB_DEVICE(USB_VENDOR_ID_APPLE, USB_DEVICE_ID_APPLE_IRCONTROL4) },
> > { HID_USB_DEVICE(USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_LCM)},
> > { HID_USB_DEVICE(USB_VENDOR_ID_ASUS, USB_DEVICE_ID_ASUS_LCM2)},
> > { HID_USB_DEVICE(USB_VENDOR_ID_AVERMEDIA, USB_DEVICE_ID_AVER_FM_MR800) },
>
> My impression is that this would break existing lirc setups that use
> the macmini lirc userspace driver which relies on a HID device, right?
Yes, which I mentioned could be worked around using usbhid.quirks on
boot (if you need the extra key definitions), or using lirc's uinput
driver (if you're using the stock hardware).
next prev parent reply other threads:[~2010-01-18 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 14:14 [PATCHes] Apple IR receiver driver Bastien Nocera
2010-01-18 14:34 ` Tino Keitel
2010-01-18 14:51 ` Bastien Nocera [this message]
2010-01-18 15:48 ` Tino Keitel
2010-01-18 16:07 ` Bastien Nocera
2010-01-18 16:19 ` Tino Keitel
2010-01-18 16:36 ` Bastien Nocera
2010-01-18 16:39 ` Jarod Wilson
2010-01-18 16:43 ` Tino Keitel
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=1263826271.20565.2769.camel@localhost.localdomain \
--to=hadess@hadess.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=tino.keitel@gmx.de \
--cc=tino.keitel@tikei.de \
/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).