On Thu, 25 Sep 2008, Mauro Carvalho Chehab wrote: >> How would it work with the key-table onces it is done with hidraw? > > Patrick, > > If implemented properly, key code tables can be replaced anytime in > userspace. > > We have already a tool for this, under v4l2-apps/util. It is called keytable. > The tool can be used to get the current key association of an input device, > generating a text file, or to load a text file into an input device. > > When you build the tool, the Makefile will parse several keycode tables > already existing on V4L and at the common IR files, writing them into > keycodes/ dir. It would be really easy to parse other files and create their > tables as well. 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? What do you think? Patrick. -- Mail: patrick.boettcher@xxxxxxx WWW: http://www.wi-bw.tfh-wildau.de/~pboettch/ _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
