Date: Thu, 27 Oct 2016 18:39:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 213835] bhyve patch: sent ps/2 scancodes for NumLock, ScrollLock and numerical keypad keys. Message-ID: <bug-213835-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213835 Bug ID: 213835 Summary: bhyve patch: sent ps/2 scancodes for NumLock, ScrollLock and numerical keypad keys. Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: ivan.zhmudo@gmail.com Keywords: patch Created attachment 176222 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D176222&action= =3Dedit The patch Hello. I've noticed, that bhyve (at least when it works in conjunction with= VNC client) does not understand *lock and keypad keys and prints debug messages like "Unhandled ps2 keyboard keysym". Suggesting a patch which seems to fix= the problem. Also, can you please explain what uint32_t keysym codes are? The first 127 = of them seem to be ASCII codes and translation table contain ASCII->PS/2 set 2 scancode mappings. But why TAB,ESC and some other symbols are coded with leading 0xff? For example, TAB is 0xff09. How keysyms are generated for *lo= ck and Keypad keys? Nevertheless, I wrote the patch using the mentioned debug output. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213835-8>