From owner-freebsd-bugs Wed Oct 23 18:23:44 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA25655 for bugs-outgoing; Wed, 23 Oct 1996 18:23:44 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA25643 for ; Wed, 23 Oct 1996 18:23:38 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.7.6/8.6.9) id LAA23314; Thu, 24 Oct 1996 11:20:02 +1000 Date: Thu, 24 Oct 1996 11:20:02 +1000 From: Bruce Evans Message-Id: <199610240120.LAA23314@godzilla.zeta.org.au> To: bde@zeta.org.au, julian@whistle.com Subject: Re: kern/1868: keyboard leds Cc: freebsd-bugs@freefall.freebsd.org Sender: owner-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> Previously it told me that I had no keyboard, and didn't >> print anything for the LED errors, but I had a keyboard, >> and everything except setting the LEDs worked. >COuldn't it be less verbose if there's a chance that >there is no keyboard? That would require more code to keep track of whether it might not have a keyboard, and further delay the complete fix of keeping track of whether it has a keyboard and not issueing keyboard commands when it doesn't have one. (The keyboard interrupts and sends a recognisable scan code when it is plugged in (the same one as for completion of the reset command IIRC). The driver should synchronize the external state with its state when it receives this scan code.) Bruce