On Mon, Jun 23, 2014 at 12:57 PM, Doug Anderson <dianders@xxxxxxxxxxxx> wrote: >> Also when the screen stayed on, the embedded controller's keymap seems >> hardcoded to US English with system settings not taking effect; but >> surely we don't want per-keyboard device tree files to remedy that. > > +Benson may be able to answer this. I believe generally non-US > keyboard layouts are handled at a higher level. There's no such thing as a notion of US versus non-US keyboard layouts at the embedded controller level or even in the kernel. Indeed, this should all be handled in user space. The chromeos firmware and kernel should return the correct key codes for every key pressed on keyboards with the ANSI layout (US based), or ISO (UK and most other countries). The only differences are : * the ISO keyboard has an extra key, which is immediately to the right of the Left Shift key. This must return KEY_102ND key code from the input layer. * the ISO keyboard has a different location for the | \ key, which accomodates the upside L shaped Enter key on the right side of the keyboard. The keycode for this key is KEY_BACKSLASH. Basically, all of this should be verified using evtest to test that the ec and kernel have the keys right. If you are having other problems with keyboard layout being stuck to US QWERTY, please check your user space. -- Benson Leung Software Engineer, Chrom* OS bleung@xxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |