Re: [RFC PATCH 0/2] Apple remote support

[Jarod Wilson <jarod@redhat.com>]

On Fri, Oct 29, 2010 at 09:17:11PM +0200, David Härdeman wrote:
> On Fri, Oct 29, 2010 at 11:11:41AM -0400, Jarod Wilson wrote:
> > So the Apple remotes do something funky... One of the four bytes is a
> > remote identifier byte, which is used for pairing the remote to a specific
> > device, and you can change the ID byte by simply holding down buttons on
> > the remote.
> 
> How many different ID's are possible to set on the remote?

256, apparently.

> > We could ignore the ID byte, and just match all Apple remotes,
> > or we could add some sort of pairing support where we require the right ID
> > byte in order to do scancode -> keycode mapping... But in the match all
> > case, I think we need the NEC extended scancode (e.g. 0xee8703 for KEY_MENU
> > on my remote), while in the match paired case, we need the full
> > 4-byte/32-bit code... Offhand, I'm not quite sure how to cleanly handle
> > both cases.
> 
> If the number of possible ID values is not obscene, you could report the 
> full 32 bit scancode and have a keymap with all the different 
> variations.

I'm thinking 256 * 6 is probably a bit obscene, but I guess that way, you
could work with all remotes if desired, and to "pair", just remove all but
the 6 for your remote... I'll keep giving it some thought, I feel like we
ought to have a cleaner way to do this.

-- 
Jarod Wilson
jarod@redhat.com