From owner-freebsd-current@FreeBSD.ORG Mon Feb 27 18:13:55 2006 Return-Path: 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 5F4DD16A420 for ; Mon, 27 Feb 2006 18:13:55 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7A4243D49 for ; Mon, 27 Feb 2006 18:13:54 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id k1RIDrM17022 for ; Mon, 27 Feb 2006 13:13:54 -0500 Message-ID: <44034160.8060905@savvis.net> Date: Mon, 27 Feb 2006 10:13:52 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Subject: [PATCH] upcoming kbdmux(4) integration X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Feb 2006 18:13:55 -0000 Dear Hackers, the bug, causing hard lockup with kbdmux(4), atkbd(4) and psm(4), was fixed in both releng_6 and head. i'd like to go ahead and integrate kbdmux(4) with the kbd code and syscons(4). also i'd like to make kbdmux(4) default in -current. please comment on the following patch http://people.freebsd.org/~emax/kbdmux.diff.txt (freefall:~emax/kbdmux.diff.txt) this is one of the earlier kbdmux(4) patches and parts of it have already been integrated into the source tree. it will probably not apply cleanly onto current source tree, however the intension is just to give general idea. 1) syscons(4) will try to look for kbdmux(4) keyboard first, and then, if not found, look for any keyboard; 2) kbd code is modified so if kbdmux(4) is the current keyboard, all new keyboards are automatically added to the kbdmux(4); 3) switch to kbdmux(4) can be done at boot time, by loading kbdmux module, or at run time, by kldload'ing kbdmux and releasing current active keyboard; 4) if, for whatever reason, kbdmux(4) is not required/desired then just do not load it and everything should work as before. thanks, max