qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v6 1/4] hw: convert virtio-input-hid device to k


From: Anthony PERARD
Subject: Re: [Qemu-devel] [PATCH v6 1/4] hw: convert virtio-input-hid device to keycodemapdb
Date: Wed, 13 Dec 2017 15:04:55 +0000
User-agent: Mutt/1.9.1 (2017-09-22)

On Tue, Dec 12, 2017 at 02:10:41PM +0000, Daniel P. Berrange wrote:
> diff --git a/Makefile b/Makefile
> index ab0354c153..5aaff5fe1e 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -227,6 +227,7 @@ KEYCODEMAP_CSV = 
> $(SRC_PATH)/ui/keycodemapdb/data/keymaps.csv
>  
>  KEYCODEMAP_FILES = \
>                ui/input-keymap-linux-to-qcode.c \
> +              ui/input-keymap-qcode-to-linux.c \
>                ui/input-keymap-qcode-to-qnum.c \
>                ui/input-keymap-qnum-to-qcode.c \
>                $(NULL)

FYI, there is a patch on the mailing list that does just generate the
new keymap:
<address@hidden>
([PATCH v5 1/4] ui: generate qcode to linux mappings)

> diff --git a/include/ui/input.h b/include/ui/input.h
> index f8cee43f65..6f56d868c7 100644
> --- a/include/ui/input.h
> +++ b/include/ui/input.h
> @@ -71,6 +71,9 @@ void qemu_remove_mouse_mode_change_notifier(Notifier 
> *notify);
>  extern const guint qemu_input_map_linux_to_qcode_len;
>  extern const guint16 qemu_input_map_linux_to_qcode[];
>  
> +extern const guint qemu_input_map_qcode_to_linux_len;
> +extern const guint16 qemu_input_map_qcode_to_linux[];
> +
>  extern const guint qemu_input_map_qcode_to_qnum_len;
>  extern const guint16 qemu_input_map_qcode_to_qnum[];
>  
> diff --git a/ui/input-keymap.c b/ui/input-keymap.c
> index 3a19a169f5..6e543d651f 100644
> --- a/ui/input-keymap.c
> +++ b/ui/input-keymap.c
> @@ -6,6 +6,7 @@
>  #include "standard-headers/linux/input.h"
>  
>  #include "ui/input-keymap-linux-to-qcode.c"
> +#include "ui/input-keymap-qcode-to-linux.c"
>  #include "ui/input-keymap-qcode-to-qnum.c"
>  #include "ui/input-keymap-qnum-to-qcode.c"

-- 
Anthony PERARD



reply via email to

[Prev in Thread] Current Thread [Next in Thread]