Re: [media] rc-core: move timeout and checks to lirc

["David Härdeman" <david@hardeman.nu>]

On Mon, Aug 20, 2012 at 06:10:16PM -0400, Devin Heitmueller wrote:
>On Mon, Aug 20, 2012 at 6:02 PM, Mauro Carvalho Chehab
><mchehab@redhat.com> wrote:
>> So, IMO, it makes sense to have a "high end" API that accepts
>> writing keystrokes like above, working with both "raw drivers"
>> using some kernel IR protocol encoders, and with devices that can
>> accept "processed" keystrokes, like HDMI CEC.
>
>It might also make sense to have a third mode for devices that support
>high level protocols such as RC5/NEC but you want to leverage the very
>large existing LIRC database of remote controls.  The device would
>advertise all the modes it supports (RC5/NEC/RC6/whatever), and from
>there it can accept the actual RC codes instead of a raw waveform.

That should be pretty trivial with the API I suggested - i.e. that
userspace is expected to do an ioctl first to get the bitmask of
supported modes. This would just be another TX mode.


-- 
David Härdeman