Re: keymap nl-be bug/incomplete

[Avi Kivity <avi@qumranet.com>]

Ben Budts wrote:
> Hi,
>
> I've been having problems using the -vnc and -k nl-be... Since I've started using KVM v.28 ...
>
> Lots of keys won't work and you get the following errors in your Host OS :
>
> Warning: no scancode found for keysym 249
> Warning: no scancode found for keysym 163
> Warning: no scancode found for keysym 163
> Warning: no scancode found for keysym 163
> Warning: no scancode found for keysym 163
> Warning: no scancode found for keysym 224
> Warning: no scancode found for keysym 224
> Warning: no scancode found for keysym 224
> Warning: no scancode found for keysym 224
> Warning: no scancode found for keysym 231
>
>
> I'm running version 61 now and the keymap still hasn't been fixed, so
> I took the liberty to change the original nl-be keymap that looks like this :
>
> nato:/opt/kvm/share/qemu/keymaps# cat nl-be
> # Dutch (Belgium)
> map 0x813
> include common
> -----------------------------------------------------
> Did some hard work and added the following, which solved all my problems :-)
> Would be great if you could implement it in your new KVM release
>   

This problem is probably shared with qemu, so please post this to 
qemu-devel@nongnu.org.  I'll merge it into kvm within a few days.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/