Re: [Xen-devel] [RFC] keymap support for PVFB

["Junko Ichino" <ichino.junko@xxxxxxxxxxxxxx>]

Hi Markus,

PVFB does the same conversion (keysym->scancode) as qemu-dm. 
Conversion is correctly done in qemu-dm of original, 
and "\" is displayed on the screen. 

When keysym was 92,  I handed 43 compulsorily to scancode.
The result is as follows. 

PVFB:
keycode 92(0x5C) -> scancode 43

xev:
keycode 51    keysym 0x5d, bracketright


Thanks,
-
Junko Ichino


----- Original Message ----- 
From: "Markus Armbruster" <armbru@xxxxxxxxxx>
To: "Junko Ichino" <ichino.junko@xxxxxxxxxxxxxx>
Cc: <Xen-devel@xxxxxxxxxxxxxxxxxxx>
Sent: Wednesday, January 17, 2007 4:48 PM
Subject: Re: [Xen-devel] [RFC] keymap support for PVFB


> "Junko Ichino" <ichino.junko@xxxxxxxxxxxxxx> writes:
>
> > Hi Markus,
> >
> > I checked that the result of conversion had passed PVFB and gone out of
> > fbflont.
> > I think that the conversion by the OS side will go wrong.
> >
> > If you know how it will pass from guest OS to guest OS's X,
> > please give me some comments.
> >
> > When I input "\",  following message a display each modules
> >
> > PVFB:
> > keycode 92(0x5C) -> scancode 115
> >
> > xev:
> > keycode 176   keysym 0x0, NoSymbol
> Let's make sure I got the facts right:
>
> Your vncfb backend receives key symbol 92 (XK_backslash) from your VNC
> viewer.
>
> Your vncfb translates that to Linux input layer key code 115.
>
> Is that what happens?
>
> Key code 115 is KEY_VOLUMEUP.  That's wrong.  You want 43
> (KEY_BACKSLASH) instead.  Bug in your translation table?
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel