From owner-freebsd-current@FreeBSD.ORG  Sat Feb 25 16:32:56 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-current@freebsd.org
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 4058516A422
	for <freebsd-current@freebsd.org>; Sat, 25 Feb 2006 16:32:56 +0000 (GMT)
	(envelope-from maksim.yevmenkin@savvis.net)
Received: from mta11.adelphia.net (mta11.adelphia.net [68.168.78.205])
	by mx1.FreeBSD.org (Postfix) with ESMTP id DCDFA43D48
	for <freebsd-current@freebsd.org>; Sat, 25 Feb 2006 16:32:55 +0000 (GMT)
	(envelope-from maksim.yevmenkin@savvis.net)
Received: from [192.168.1.254] (really [70.32.199.60]) by mta11.adelphia.net
	(InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP
	id <20060225163255.UGMV17101.mta11.adelphia.net@[192.168.1.254]>;
	Sat, 25 Feb 2006 11:32:55 -0500
Message-ID: <440086AC.8090600@savvis.net>
Date: Sat, 25 Feb 2006 08:32:44 -0800
From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net>
User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ulrich Spoerlein <q@galgenberg.net>
References: <43FF986E.9030205@savvis.net>
	<20060225151031.GA1088@galgenberg.net>
In-Reply-To: <20060225151031.GA1088@galgenberg.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-current@freebsd.org
Subject: Re: [PATCH] kbdmux(4) update
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Feb 2006 16:32:56 -0000

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