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 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
