On Sat, Oct 30, 2010 at 10:32:14PM -0400, Jarod Wilson wrote: > On Sat, Oct 30, 2010 at 7:36 PM, David Härdeman <david@xxxxxxxxxxx> wrote: > > In that case, one solution would be: > > > > * using the full 32 bit scancode > > * add a module parameter to squash the ID byte to zero > > * default the module parameter to true > > * create a keymap suitable for ID = 0x00 > > > > Users who really want to distinguish remotes can then change the module > > parameter and generate a keymap for their particular ID. Most others > > will be blissfully unaware of this feature. > > I was thinking something similar but slightly different. I think ID = > 0x00 is a valid ID byte, so I was thinking static int pair_id = -1; to > start out. This would be a stand-alone apple-only decoder, so we'd > look for the apple identifier bytes, bail if not found. We'd also look > at the ID byte, and if pair_id is 0-255, we'd bail if the ID byte > didn't match it. The scancode we'd actually use to match the key table > would be just the one command byte. It seems to make sense in my head, > at least. But you'd lose the ability to support two different remotes with different ID's (if you want different mappings in the keymap). -- David Härdeman -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
