Hello,
One problem in embedded world is that people want the same thing with a PC.
Two solutions are available :
- first we create from scratch every things. Then the software works fine
on the target but it's the "wild west"... :-) and it's bad for the
innovation.
- second we use libraries from
On Tue, Jun 18, 2013 at 4:15 AM, Marc Chalain wrote:
> Hello,
> linux/input.h gives numbers of key definitions. The keymap is only useful
> for PC keyboard when only the layout change from one country to an other. On
> device we have : on/off, softkey1, softkey2, 12 keys for the keypad in some
> c
Hello,
linux/input.h gives numbers of key definitions. The keymap is only useful
for PC keyboard when only the layout change from one country to an other.
On device we have : on/off, softkey1, softkey2, 12 keys for the keypad in
some cases, home, back... The key codes are hard coded inside the kern
On Mon, 2013-06-17 at 18:08 +0200, Marc Chalain wrote:
> Hello,
> My first observation is we need a PC keyboard support at the end
> ( often a virtual keyboard).
There's an input method procotol that we intended to use for virtual
keyboards. Try weston's clients/editor.c together with the exampl
Hi Marc,
On 17 June 2013 17:08, Marc Chalain wrote:
> I already wrote an email on this mailing list about the use of xkbcommon for
> embedded solution.
> I had the same problem as Robert, and I disabled the check of the keymap.
> The problem is that we have number of keyboards as input device, on
Hello,
I already wrote an email on this mailing list about the use of xkbcommon
for embedded solution.
I had the same problem as Robert, and I disabled the check of the keymap.
The problem is that we have number of keyboards as input device, on the
same platform, and it's not possible to define a
