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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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?

> 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.

-- 
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux