On Fri, 26 Sep 2008, Patrick Boettcher wrote: > That sounds great, though I would prefer a more generic solution if it > exists/will exist. > > Assuming I would go with this one: how could I make sure, that I don't break > support for existing users? Is there a way to request/suggest a certain > keymap from the kernel module, depending on the device's default. > > If not, I think we have problem - we shall not forget, we are plumbers ;). > > Maybe the solution is to go with this model in the future and keep the > current keymaps where they are? I think so. Just removing the keycodes will break backward compat. > What do you think? I think that some plumbering is needed to automate keycode load. There's no daemon or script that uses this. I think that we should discuss this with udev guys. Ideally, a udev rule may run an userspace program to detect the hardware type and load the default key. This program should check for some /etc/sysconfig file to see if it should load a non-default keytable. Inside the kernel, all you need is to use the default event interface. If I remember well, for this to work, you need to inform input layer about the size of the IR table. There's a helper function used by V4L and some DVB devices at: common/ir-functions.c: ir_input_init() If you want users to allow changing IR tables dynamically, the better is to use IR_KEYTAB_SIZE for the key size on all IR's. This way programable IR's with lots of keycodes can also be used. Cheers, Mauro _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
