Date: Wed, 03 Jan 2007 15:45:31 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: John Baldwin <jhb@freebsd.org> Cc: Greg 'groggy' Lehey <grog@freebsd.org>, current@freebsd.org Subject: Re: How to resolve problems in our software Message-ID: <459C401B.20005@savvis.net> In-Reply-To: <200701031758.31576.jhb@freebsd.org> References: <459B5CA9.4070909@root.org> <20070103124106.U82671@maildrop.int.zabbadoz.net> <20070103223621.GX78631@wantadilla.lemis.com> <200701031758.31576.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > [ moved to current@ ] > > On Wednesday 03 January 2007 17:36, Greg 'groggy' Lehey wrote: >> So: we have a problem with kbdmux, which looks suspiciously like a >> bug. I don't know this code, but it seems to have been there for a >> while. How, in your opinion, do I go about fixing it? > > So it's not clear from your original message how you are using kbdcontrol and > kbdmux. It sounds like you want the USB keyboard (when present) to be the > normal keyboard for syscons and atkbd0 to be left alone for use by a specific > process, yes? Can't you just do 'kbdcontrol -A atkbd0 < /dev/kbdmux0' once not /dev/kbdmux0 - it is a keyboard device (just like /dev/ukb0 and /dev/atkbd0) and it will be busy because syscons already got kbdmux as its main keyboard. please use < /dev/console or < /dev/ttyv0. > during boot and be done? The default for the USB keyboard should be for it > to be added to kbdmux0 and thus result in it being used for the regular > console without any special magic needed. other then above comment everything else is correct and i suggested the same in private email. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?459C401B.20005>