Re: [PATCH] kbdmux(4) update
- From: Maksim Yevmenkin <maksim.yevmenkin@xxxxxxxxxx>
- Date: Sat, 25 Feb 2006 08:32:44 -0800
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
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- References:
- [PATCH] kbdmux(4) update
- From: Maksim Yevmenkin
- [PATCH] kbdmux(4) update
- Prev by Date: Re: [PATCH] kbdmux(4) update
- Next by Date: Re: [PATCH] kbdmux(4) update
- Previous by thread: Re: [PATCH] kbdmux(4) update
- Next by thread: Re: [PATCH] kbdmux(4) update
- Index(es):