From owner-freebsd-current Sun May 12 03:20:50 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA12530 for current-outgoing; Sun, 12 May 1996 03:20:50 -0700 (PDT) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA12517 for ; Sun, 12 May 1996 03:20:45 -0700 (PDT) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA29350 for ; Sun, 12 May 1996 12:20:38 +0200 Received: by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA22399 for freebsd-current@FreeBSD.org; Sun, 12 May 1996 12:20:37 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.7.5/8.6.9) id MAA06566 for freebsd-current@FreeBSD.org; Sun, 12 May 1996 12:04:56 +0200 (MET DST) From: J Wunsch Message-Id: <199605121004.MAA06566@uriah.heep.sax.de> Subject: Re: cvs commit: src/sys/i386/isa syscons.c To: freebsd-current@FreeBSD.org (FreeBSD-current users) Date: Sun, 12 May 1996 12:04:55 +0200 (MET DST) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199605120211.MAA13485@godzilla.zeta.org.au> from Bruce Evans at "May 12, 96 12:11:41 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL15 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk (moved to -current) As Bruce Evans wrote: > > Give up waiting for a successful keyboard reset after some > > unreasonable time. I've got a PCI mainboard that simply doesn't grok > > it, so continuing with a warning (and a keyboard that's working > > nevertheless :) seems to be better than spin-looping forever. > > Does it work if you fix the well known `!retries' logic bug (the infinite > loop always gets entered if the first loop fails (retries == -1)). No, retries were at 4 when the probe went on. (Well, damn, i could have fixed the retries bug in the same commit.) I've single-stepped the code in DDB, and this keyboard controller always responded with ``keyboard buffer empty'' (first infinite loop) and the byte 0xfa was fetched (KB_ACK, second infinite loop). It suprised me a bit, since it was just an AMIKEY-2 controller as i've seen it working on many other boards before. Alas, the chip has been soldered in (and the board itself was a loaner to me only to debug this problem -- so i couldn't use a soldering iron :), so replacing it was not an option for me. > I have a keyboard with a partly broken cable or connector which causes > interesting problems for keyboard drivers. The BIOS keyboard driver > seems to handle transient disconnections better than syscons. Perhaps > it issues a reset when the keyboard stops working. Perhaps the BIOS reacts properly to the 0xaa (SELF TEST OKAY) message that is sent when the keyboard plugs in, and re-initializes the keyboard. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)