From owner-freebsd-current@FreeBSD.ORG  Sat Feb 25 20:32:23 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 DFAF616A422
	for <freebsd-current@freebsd.org>; Sat, 25 Feb 2006 20:32:23 +0000 (GMT)
	(envelope-from scottl@samsco.org)
Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6CFF343D46
	for <freebsd-current@freebsd.org>; Sat, 25 Feb 2006 20:32:19 +0000 (GMT)
	(envelope-from scottl@samsco.org)
Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11])
	(authenticated bits=0)
	by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k1PKWC2U026301;
	Sat, 25 Feb 2006 13:32:12 -0700 (MST)
	(envelope-from scottl@samsco.org)
Message-ID: <4400BECB.8080406@samsco.org>
Date: Sat, 25 Feb 2006 13:32:11 -0700
From: Scott Long <scottl@samsco.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20051230
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Markus Brueffer <markus@brueffer.de>
References: <43FF986E.9030205@savvis.net>	<200602251538.54403.markus@brueffer.de>	<4400840F.3030807@savvis.net>
	<200602251811.50530.markus@brueffer.de>
In-Reply-To: <200602251811.50530.markus@brueffer.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed 
	version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org
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 20:32:24 -0000

Markus Brueffer wrote:
> Am Saturday 25 February 2006 17:21 schrieb Maksim Yevmenkin:
> 
>>>>the following patch should fix the problem with kbdmux(4). please give
>>>>it a try and let me know if it works for you.
>>>
>>>[...]
>>>
>>>Great work! With this patch I'm currently working since half an hour with
>>>a PS/2 mouse, a Bluetooth mouse, a PS/2 keyboard and a Bluetooth mouse in
>>>parallel without any ill effects. Without it, the machine froze within
>>>seconds.
>>
>>cool, thanks for the report. btw, did you mean "ps/2 keyboard and a
>>bluetooth keyboard" (not mouse) above? or you really have 2 bluetooth
>>mice going at the same time?
> 
> 
> Actually I meant "ps/2 keyboard and a bluetooth keyboard", but I did a little 
> bit of further testing and now have:
> 
>  - one Logitech ps/2 mouse
>  - one Logitech MX1000 bluetooth mouse
>  - two Logitech MX900 bluetooth mice
>  - one Cherry ps/2 keyboard
>  - one Logitech MX5000 bluetooth keyboard
> 
> working in parallel flawlessly :) I would say: Awesome work Maksim!
> 
> 
>>>Btw: I'm getting LORs from vkbd(4) when working with the bluetooth
>>>keyboard (6-STABLE from about an hour ago with the kndmux patch):
>>
>>thanks for reporting this. it has nothing to do with the kdbmux(4)
>>patch. it has been there for quite a long time. i will fix it.
> 
> 
> Thanks!
> 
> Markus
> 

This is definitely something worth getting into 6.1.

Scott