On Di, 2015-05-26 at 18:24 -0300, Joao Luis Meloni Assirati wrote:
> Hello,
>
> > I've tested an unpatched QEMU 2.3.0 (x86_64) with "-k pt_br" option and
> > the
> > "/?°" key works perfectly.
>
> From the manpage of qemu:
>
> -k language
>Use keyboard layout language (for example "fr" for
Hi,
> >> 12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was
> >> pressed
> >> 12:44:04.253486: EV_KEY KEY_KPCOMMA (0x79) pressed
> >
> > Ok. Is there a key with ',' too in your numpad?
>
> Yes, there is a separated ',' in the numpad, and when I press it I get
>
> 17:48:47.8
Hello,
> I've tested an unpatched QEMU 2.3.0 (x86_64) with "-k pt_br" option and
> the
> "/?°" key works perfectly.
>From the manpage of qemu:
-k language
Use keyboard layout language (for example "fr" for French). This option
is only needed where it is not easy to get raw PC keycodes (e.g.
Hello,
>> 12:44:02.389552: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
>> 12:44:02.389552: EV_KEY KEY_RO (0x59) pressed
>
> 'RO'. Hmm, not very descriptive. Any idea what this could stand for?
RO stands for Romaji, which is japanese with roman letters (transliteration).
>
>> 12:44:04.253486
I've tested an unpatched QEMU 2.3.0 (x86_64) with "-k pt_br" option and the
"/?°" key works perfectly.
I have not tested the numpad ".", but I can inform that ABNT2 keyboard does
have "." (dot) and "," (comma) as separate keys: comma (numlock on)
combined with delete (numlock off).
But I found an
> static const uint8_t evdev_keycode_to_pc_keycode[61] = {
> -0, /* 97 EVDEV - RO ("Internet" Keyboards) */
> +0x73, /* 97 EVDEV - /? (ABNT2 Keyboards) */
That one looks good.
> -0, /* 129 EVDEV - I129 ("Internet" Keyboards) */
> +0x34, /* 129 abnt2
Hi,
> 12:44:02.389552: EV_MSC MSC_SCAN 458887 <== Here, / was pressed
> 12:44:02.389552: EV_KEY KEY_RO (0x59) pressed
'RO'. Hmm, not very descriptive. Any idea what this could stand for?
> 12:44:04.253486: EV_MSC MSC_SCAN 458885 <== Here, . in the numpad was pressed
> 12:44:04.253486: EV_KEY
>> > Anyone having such a keyboard and willing to run some tests?
[...]
> (c) Then use 'input-events ' to get a input event log
> printed to the terminal. Type each missing key once.
>
> (d) Send me the log (with annotation which key is which).
There are two missing keys: / (which is also ?
> 22.05.2015 13:01, Gerd Hoffmann wrote:
[...]
The solution appears to be trivial (see also some background
at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
but the problem is definitely still here.
This is the patch that works:
--- ui/x_keymap.c~
+++ ui/x_ke
22.05.2015 16:20, Gerd Hoffmann wrote
> Hi,
>
>>> Anyone having such a keyboard and willing to run some tests?
>>
>> Adding Cc's. This has been reported to debian too,
>> http://bugs.debian.org/772422 (also in Cc).
>
> Ok, so just replying should stick this into the debian bug tracker, right?
Hi,
> > Anyone having such a keyboard and willing to run some tests?
>
> Adding Cc's. This has been reported to debian too,
> http://bugs.debian.org/772422 (also in Cc).
Ok, so just replying should stick this into the debian bug tracker,
right?
Ok, instructions are here:
(a) Go grab https:/
22.05.2015 13:01, Gerd Hoffmann wrote:
> On Mi, 2015-05-20 at 14:44 +0300, Michael Tokarev wrote:
>> A (friendly) ping? :)
>>
>>> The solution appears to be trivial (see also some background
>>> at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
>>> but the problem is definitely
On Mi, 2015-05-20 at 14:44 +0300, Michael Tokarev wrote:
> A (friendly) ping? :)
>
> > The solution appears to be trivial (see also some background
> > at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
> > but the problem is definitely still here.
> >
> > Maybe it's a time to
A (friendly) ping? :)
30.04.2015 08:01, Michael Tokarev wrote:
> There's a bug open in qemu bugtracker for several years
> already, https://bugs.launchpad.net/qemu/+bug/1038136 .
> The solution appears to be trivial (see also some background
> at http://blog.nielshorn.net/2011/03/qemu-and-brazilia
There's a bug open in qemu bugtracker for several years
already, https://bugs.launchpad.net/qemu/+bug/1038136 .
The solution appears to be trivial (see also some background
at http://blog.nielshorn.net/2011/03/qemu-and-brazilian-keyboards/ ),
but the problem is definitely still here.
Maybe it's a
15 matches
Mail list logo
