On Thu, Nov 18, 2010 at 09:43:19PM +0100, David Härdeman wrote: > On Thu, Nov 18, 2010 at 11:33:04AM -0500, Jarod Wilson wrote: > >Mauro's suggestion, iirc, was that max scancode size should be a > >property of the keytable uploaded, and something set at load time (and > >probably exposed as a sysfs node, similar to protocols). > > I think that would be a step in the wrong direction. It would make the > keytables less flexible while providing no real advantages. I think it was supposed to be something you could update on the fly when uploading new keys, so its not entirely inflexible. Default keymap might be 24-bit NEC, then you upload 32-bit NEC codes, and the max scancode size would get updated at the same time. Of course, it probably wouldn't work terribly well to have a mix of 24-bit and 32-bit NEC codes in the same table. -- Jarod Wilson jarod@xxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
