From: "Andreas Färber" <afaerber-l3A5Bk7waGM@public.gmane.org>
To: Benson Leung <bleung-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
linux-samsung-soc
<linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Stephan van Schaik
<stephan-zGZ7W/ttz6xN8Ch2cx6nig@public.gmane.org>,
Vincent Palatin
<vpalatin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>,
openSUSE ARM ML
<opensuse-arm-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org>
Subject: Re: [RFC 0/4] ARM: dts: exynos: Prepare Spring
Date: Mon, 23 Jun 2014 23:24:28 +0200 [thread overview]
Message-ID: <53A89B0C.5000206@suse.de> (raw)
In-Reply-To: <CANLzEksRmsk1y2ZEjRVE8F8DjSUeW3AebaaDWL71Z4Gc9NvZeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Am 23.06.2014 22:11, schrieb Benson Leung:
> On Mon, Jun 23, 2014 at 12:57 PM, Doug Anderson <dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org> 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.
Hm, we may be talking about two different things here? I have been doing
a minimum system bring-up for 3.16, with openSUSE userspace.
My YaST-selected system keymap (German with deadkeys) is not taking
effect on German Spring at the *framebuffer console* (tty1) - evdev is
not involved at that level AIUI.
Backspace and L-shaped enter keys work okay. The keymap here should be
identical to that in the original German device and seemed to match that
in the exynos5250-snow.dts file.
I just checked (w/ dp-controller, hdmi, fimd commented out in my patch):
* An external USB keyboard does not work correctly either.
* In X11 (xdm), both internal and USB keyboard work as expected.
Similar situation in ChromeOS IIRC, with keymap correct at graphical
login but not on the right-arrow console - although I don't know the
ChromeOS userland too well to judge if it was configured correctly.
> If you are having other problems with keyboard layout being stuck to
> US QWERTY, please check your user space.
On my Raspberry Pi for instance, the equivalent openSUSE Factory works
just fine with German keymap for USB keyboard. Might any related kernel
config options be missing in exynos_defconfig? Anything in particular I
should check in user space?
Cheers,
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
--
To unsubscribe, e-mail: opensuse-arm+unsubscribe-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org
To contact the owner, e-mail: opensuse-arm+owner-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org
next prev parent reply other threads:[~2014-06-23 21:24 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 1:21 [RFC 0/4] ARM: dts: exynos: Prepare Spring Andreas Färber
2014-06-23 1:21 ` [PATCH 1/4] Documentation: devicetree: Fix s2mps11 and s5m8767 typos Andreas Färber
2014-06-23 1:21 ` Andreas Färber
2014-06-23 3:21 ` Sachin Kamat
2014-06-23 23:06 ` Andreas Färber
2014-06-23 23:20 ` Doug Anderson
2014-06-23 8:15 ` Lee Jones
2014-06-23 1:21 ` [PATCH 2/4] Documentation: devicetree: Fix s2mps11 example syntax Andreas Färber
2014-06-23 1:21 ` Andreas Färber
2014-06-23 3:23 ` Sachin Kamat
2014-06-23 8:15 ` Lee Jones
2014-06-23 1:21 ` [PATCH 3/4] Documentation: devicetree: Fix tps65090 typos Andreas Färber
2014-06-23 1:21 ` Andreas Färber
2014-06-23 17:27 ` Doug Anderson
2014-06-25 10:47 ` Mark Rutland
2014-06-25 11:43 ` Andreas Färber
2014-06-25 12:23 ` Rob Herring
2014-06-23 1:21 ` [RFC 4/4] ARM: dts: exynos5250: Add Spring device tree Andreas Färber
2014-06-23 1:21 ` Andreas Färber
2014-06-23 1:21 ` Andreas Färber
2014-06-23 19:47 ` Doug Anderson
2014-06-23 19:47 ` Doug Anderson
2014-06-23 22:46 ` Andreas Färber
2014-06-23 22:46 ` Andreas Färber
2014-06-24 4:05 ` Doug Anderson
2014-06-24 4:05 ` Doug Anderson
[not found] ` <CAD=FV=W96QpDhh1NSaVwrXYjL6Jr-v4sq1-eRSfT=tErw_KCOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-24 10:06 ` Javier Martinez Canillas
2014-06-24 10:06 ` Javier Martinez Canillas
2014-06-24 10:06 ` Javier Martinez Canillas
2014-06-24 15:20 ` Doug Anderson
2014-06-24 15:20 ` Doug Anderson
2014-06-24 15:03 ` Vincent Palatin
2014-06-24 15:06 ` Vincent Palatin
2014-06-24 15:06 ` Vincent Palatin
2014-06-23 19:57 ` [RFC 0/4] ARM: dts: exynos: Prepare Spring Doug Anderson
2014-06-23 20:11 ` Benson Leung
[not found] ` <CANLzEksRmsk1y2ZEjRVE8F8DjSUeW3AebaaDWL71Z4Gc9NvZeg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-23 21:24 ` Andreas Färber [this message]
[not found] ` <53A89B0C.5000206-l3A5Bk7waGM@public.gmane.org>
2014-07-02 4:18 ` Andreas Färber
2014-07-02 14:56 ` Vincent Palatin
2014-06-24 23:18 ` Andreas Färber
2014-06-24 23:42 ` Doug Anderson
2014-06-24 23:44 ` Vincent Palatin
2014-06-24 23:56 ` Andreas Färber
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A89B0C.5000206@suse.de \
--to=afaerber-l3a5bk7wagm@public.gmane.org \
--cc=bleung-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=dianders-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-samsung-soc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=opensuse-arm-stAJ6ESoqRxg9hUCZPvPmw@public.gmane.org \
--cc=stephan-zGZ7W/ttz6xN8Ch2cx6nig@public.gmane.org \
--cc=vpalatin-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.