From: "Daniel P. Berrange" <berra...@redhat.com> Hardware scancodes are all documented in hex, so use that in trace events to make it easier to understand.
Signed-off-by: Daniel P. Berrange <berra...@redhat.com> Reviewed-by: Eric Blake <ebl...@redhat.com> Message-id: 20171019142848.572-2-berra...@redhat.com Signed-off-by: Gerd Hoffmann <kra...@redhat.com> --- hw/input/trace-events | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw/input/trace-events b/hw/input/trace-events index 6fcb3c063f..d04132d342 100644 --- a/hw/input/trace-events +++ b/hw/input/trace-events @@ -1,7 +1,7 @@ # See docs/devel/tracing.txt for syntax documentation. # hw/input/ps2.c -ps2_put_keycode(void *opaque, int keycode) "%p keycode %d" +ps2_put_keycode(void *opaque, int keycode) "%p keycode 0x%02x" ps2_read_data(void *opaque) "%p" ps2_set_ledstate(void *s, int ledstate) "%p ledstate %d" ps2_reset_keyboard(void *s) "%p" -- 2.9.3
