Krzysztof Halasa wrote: > Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> writes: > >> No. All the other API functions there work with 32 bits for scancodes. > > We don't need them, do we? We need a new ioctl for changing key mappings > anyway (a single ioctl for setting the whole table I think), and we can > have arbitrary length of scan codes there. Why do you want to replace everything into a single shot? Had you ever tried to replace a scancode table with the current API? $ wc ./keycodes/dib0700_rc_keys 216 432 3541 ./keycodes/dib0700_rc_keys This is the biggest table we have: 216 scancodes. It has codes for several different IR's bound together into the same table. Let's replace the entire table (tested on a dib8076 reference design device): $ time ./keytable ./keycodes/dib0700_rc_keys real 0m0.029s user 0m0.000s sys 0m0.027s Don't you think that 29ms to replace 216 codes to be fast enough, especially since you only need to do it once after plugging a device? Also, if you want to control your device with two different IR controllers, the better is to allow adding new keycodes there, instead of just allowing the replacement of the entire table. Maybe we'll need some extensions there, for example to extend the size of the dynamic table, but I don't see any timing issue here. Cheers, Mauro -- 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
