On Tue, 2009-12-08 at 09:32 -0200, Mauro Carvalho Chehab wrote: > Andy Walls wrote: > > On Mon, 2009-12-07 at 13:19 -0500, Jarod Wilson wrote: > > So I'll whip up an RC-6 Mode 6A decoder for cx23885-input.c before the > > end of the month. > > Good! Please, try to design the decoder as an independent module that gets > data from a kfifo and generate scancodes for the input API. Hmmm. Let me see how the protoype turns out keeping that design objective in mind. I've already got the current RC-5 and NEC decoding state machines in cx23885-input a bit layered, but they are taking advantage of specific events signaled by my v4l2_subdev implementation. Strictly speaking the state machines don't have to. All of the remote protocols I have played with make framing pretty easy. > > I can setup the CX2388[58] hardware to look for both RC-5 and RC-6 with > > a common set of parameters, so I may be able to set up the decoders to > > handle decoding from two different remote types at once. The HVR boards > > can ship with either type of remote AFAIK. > > > > I wonder if I can flip the keytables on the fly or if I have to create > > two different input devices? > > IMO, the better is, by default, to open just one input device per IR receiver. > >From what I understand from our discussions, if the user wants to filter IR > commands into several input interfaces, some userspace interface will be > provided to allow the creation of other input interfaces for that purpose. Hmm. That's not what I just thought I read from Dmitry.... Oh well. If I don'y get it done by 24 Dec, it'll be in the new year. Regards, Andy -- 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
