Date: Sat, 25 Feb 2006 13:32:11 -0700 From: Scott Long <scottl@samsco.org> To: Markus Brueffer <markus@brueffer.de> Cc: freebsd-current@freebsd.org Subject: Re: [PATCH] kbdmux(4) update Message-ID: <4400BECB.8080406@samsco.org> In-Reply-To: <200602251811.50530.markus@brueffer.de> References: <43FF986E.9030205@savvis.net> <200602251538.54403.markus@brueffer.de> <4400840F.3030807@savvis.net> <200602251811.50530.markus@brueffer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4400BECB.8080406>