> Hi, this remind me http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/584/focus=585 thread. Mauro Carvalho Chehab <mchehab <at> redhat.com> writes: > So, the basic question that should be decided is: should we create a new > userspace API for raw IR pulse/space or it would be better to standardize it > to always use the existing input layer? > To me the old ttpci approach was great : - the kernel does the IR pulse translation to input layer. In the current kernel there code duplication, it is done in many driver (with different way) [1]. A new subdriver should take as input the decoded remote address, data and toggle and output a key in input layer - userspace need to configure IR pulse type (RC5, ...), remote address, keymap. But the kernel can have some default config for the hardware. Keymap are stored in userspace. Matthieu [1] for example there not way to specify remote remote address to use. "ir->addr" hardcoded in bttv, saa7134. em28xx doesn't use the decoded rc_address, ... -- 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
