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>
Subject: Re: [PATCHes] Apple IR receiver driver
Date: Mon, 18 Jan 2010 16:36:04 +0000 [thread overview]
Message-ID: <1263832564.20565.2884.camel@localhost.localdomain> (raw)
In-Reply-To: <20100118161933.GA10491@mac.home>
On Mon, 2010-01-18 at 17:19 +0100, Tino Keitel wrote:
> On Mon, Jan 18, 2010 at 16:07:13 +0000, Bastien Nocera wrote:
> > Pass something along those lines:
> > usbhid.quirks=0xVID:0xPID:0xQUIRK
> > on the kernel command-line, and the appleir won't pick up the device,
> > and the current quirks would be restored.
>
> So I guess this would be usbhid.quirks=0x05ac:0x8240:0xsomething.
>
> The remaining question is what "something" should be.
The mask for HIDDEV and HIDINPUT_IGNORE (which I don't know on top of my
head, and will only lookup if Dmitry thinks documentation is required).
> > Given that I seriously doubt there's very many people interested in
> > using "non-standard" remotes with those receivers, it would make most
> > users' life easier (and I doubt that the people that have the hardware
> > bothered setting up lirc on their systems...).
>
> IMHO "non-standard" remotes are interesting especially with this
> remote, because the vendor supplied remote has only six keys.
Yes, and I don't know of anyone using the non-standard remotes with this
receiver, and they could still do it with a bit of tweaking (which would
be necessary to setup the other keys anyway).
> Is there really no way to make the quirk only effective if the appleir
> driver is active?
Not easily, no, though the quirks should soon be changeable at run-time,
so you could potentially not even have to reboot.
Cheers
next prev parent reply other threads:[~2010-01-18 16:36 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
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 [this message]
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=1263832564.20565.2884.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@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).