From owner-cvs-src@FreeBSD.ORG Wed Mar 1 16:30:48 2006 Return-Path: X-Original-To: cvs-src@freebsd.org Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D372116A46A; Wed, 1 Mar 2006 16:30:47 +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 381FF43D64; Wed, 1 Mar 2006 16:30:45 +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 k21GUPV3063299; Wed, 1 Mar 2006 09:30:25 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4405CC23.20403@samsco.org> Date: Wed, 01 Mar 2006 09:30:27 -0700 From: Scott Long 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: Eric Anderson References: <200602252159.k1PLxT8G036312@repoman.freebsd.org> <4400D478.7060707@samsco.org> <20060227194350.A57612@newtrinity.zeist.de> <864q2j5voi.fsf@xps.des.no> <346a80220602282337n3a2786c1qf4f9358fa6be73d4@mail.gmail.com> <44054FB8.5010707@samsco.org> <20060301135551.GY27069@submonkey.net> <4405ACE7.6060605@centtech.com> In-Reply-To: <4405ACE7.6060605@centtech.com> 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: src-committers@freebsd.org, cokane@cokane.org, cvs-src@freebsd.org, Marius Strobl , cvs-all@freebsd.org, Maksim Yevmenkin , Dag-Erling Sm?rgrav , Ceri Davies Subject: Re: cvs commit: src/sys/dev/kbdmux kbdmux.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 16:30:48 -0000 Eric Anderson wrote: > Ceri Davies wrote: > >> On Wed, Mar 01, 2006 at 12:39:36AM -0700, Scott Long wrote: >> >> >>> Coleman Kane wrote: >>> >>> >>>> On 2/28/06, *Dag-Erling Sm?rgrav* > >>>> wrote: >>>> >>>> "Maksim Yevmenkin" >>> > writes: >>>> > we should make a decision which scancodes keyboard drivers >>>> should be >>>> > returning and change kbdmux(4), syscons(4) etc. to support it. >>>> > >>>> > until then, i'm afraid, sun rs232 and powerpc adb keyboard >>>> drivers >>>> > will have to translate their own scancodes into at scancodes >>>> (just >>>> > like ukbd(4) does). >>>> >>>> Considering that ukbd(4) is the only kbd driver that runs on all >>>> platforms, it might make sense to have all other drivers translate >>>> their scancodes to ukbd(4) scancodes and use that in kbdmux(4) and >>>> syscons(4). >>>> >>>> >>>> I agree, especially since atkbdc's are rapidly being replaced by >>>> USB on the platforms they were made for. >>>> >>> >>> Long term, yes, but what is the risk/benefit of doing this for 6.1? >>> >> >> >> If it doesn't work, we look like bloody idiots. 6.2 isn't that far >> away, I'd think that anybody could manage waiting for it a little more >> (especially if it goes into RELENG_6 just after the 6.1 branch). >> >> The above not to be taken as a comment on the change, on which I am not >> informed enough to hold an opinion. >> > > > Can we have it all set, built in to GENERIC, but the device hint set to > disabled? Lots of systems, Dell PowerEdge and similar, come with a > remote access card, which uses a USB tie in. The only way I've found to > make the console keyboard work after initial install, is to boot single > user, hack /etc/devd.conf, and reboot, which is really ugly. Many > FreeBSD users get stuck with this, so it would be very nice to have a > quick way to enable the kbdmux at loader time for 6.1, but if it goes in > right after, I'm not going to cry. :) > > Thanks again Maksim for all the work on this! > > Eric > > > > I'd like to turn this on for the next BETA build, get feedback, then decide whether or not to leave it enabled for the final 6.1 release. Maksim, is that OK with you? Scott