Date: Sat, 25 Feb 2006 08:32:44 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Ulrich Spoerlein <q@galgenberg.net> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] kbdmux(4) update Message-ID: <440086AC.8090600@savvis.net> In-Reply-To: <20060225151031.GA1088@galgenberg.net> References: <43FF986E.9030205@savvis.net> <20060225151031.GA1088@galgenberg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Ulrich,
>>while i'm here, could someone please review the following patch for ukbd(4). this patch makes
>>ukbd(4) to not delay break scancodes in "raw" mode.
>
> How exactly could this manifest itself? I do have some troubles with a
it should not manifest itself if only one keyboard is used. the typical
case looks like this
"keypad-enter" is pressed and the following scancodes are sent
e0 1c e0
^prefix
^make code
^prefix
as you can see there is no "break" code. "enter" key is pressed and the
following scancodes are sent
9c 1c 9c
^break code
^make code
^delayed break code
as you can see, 0x9c is the "delayed" break code for "keypad-enter"
after ukbd(4) patch, the sequence would be
e0 1c e0 9c -- keypad-enter
1c 9c -- enter
> SUN Type5 keyboard attached via SUN->USB adapter, and I blame the USB
> stack for now. Might this lead to different scan codes "getting
> through"?
i'm not sure. imo, its not likely when only one keyboard is used. you
could try the patch and see if it fixes your problem. this patch should
not change anything else and it is pretty safe to try.
thanks,
max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440086AC.8090600>