Hi,
On Sun, 8 Feb 2009, Michael Müller wrote:
While I am indeed strongly in favor of integrating dib0700 with
ir_keymaps.c so it is consistent with the other drivers, I have been
tied up in another project and haven't had any cycles to do the work
required.
By all means, if you want to propose a patch, I would be happy to
offer feedback/comments.
Hi Devin,
yes, it was my intention to offer some help.
My hope was to find some similarities that I could use for dibcom. But
everything looks different. And they deal with GPIO. So it looks much more
complicated than just simply adding some keys to a table. ;-)
Do you have an idea which of the modules listed above is closest to the
dibcom module? Can you (easily) create a frame/template that I can use for a
start and I add details and does the testing?
Is the existing ir_keymaps approach already able to handle the case that I
need to set dvb_usb_dib0700_ir_proto=0 (=> no NEC protocol) for my Elgato?
If you are going to ir_keymap or any other superior solution (which I'm
for), please don't consider the dib0700-driver only, but think about the
whole dvb-usb-framework... Only the driver specific part can be found in
the drivers. The input-stuff is located in dvb-usb-remote.c
Loading the ir-tables from userspace would be the preferred solution, like
that any IR-receiver on any device could handle any remote-control
(requiring a generic IR-decoder in the device's firmware) without changing
the kernel-module-driver...
Is lirc already in-kernel now? Can the event-interface handle raw keys (so
that a user-space thing could translate them to their real meaning?)
Patrick.
--
Mail: patrick.boettcher@xxxxxxx
WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/
