Hi! > > > + int fifo[KBC_MAX_KPENT]; > > > + const struct tegra_kbc_platform_data *pdata; > > > + int *plain_keycode; > > > + int *fn_keycode; > > > > There should not be separate keycodes for FN and normal kys - FN is just > > a modifier, like SHIFT or CTRL or ALT are and shoudl be handled in upper > > layers. > > We had the same thought regarding Function as a modifier akin to Shift, Ctrl an Alt. > But this does not appear to be the case. > > This keyboard is used primarily for Laptop-like form factors where function keys are used to overload the existing keys. > In addition the Fn key mappings aren't identical in different keyboard layouts. > > So at this point in order to function with the target hardware and > the target operating system which is Chrome, this modifier > keymap is necessary. Please find a way to do this cleanly. Other machines (zaurus) have similar keyboards... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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
