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

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

 



On Sat, Oct 30, 2010 at 7:36 PM, David Härdeman <david@xxxxxxxxxxx> wrote:
> On Fri, Oct 29, 2010 at 04:09:37PM -0400, Jarod Wilson wrote:
>> On Fri, Oct 29, 2010 at 09:59:18PM +0200, David Härdeman wrote:
>> > On Fri, Oct 29, 2010 at 03:27:33PM -0400, Jarod Wilson wrote:
>> > > 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.
>> >
>> > Does the remote pick one for you at random?
>>
>> Looks like its randomly set at the factory, then holding a particular key
>> combo on the remote for 5 seconds, you can cycle to another one. Not sure
>> if "another one" means "increment by one" or "randomly pick another one"
>> yet though.
>
> 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.

-- 
Jarod Wilson
jarod@xxxxxxxxxxxx
--
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