From owner-freebsd-current Tue May 21 22:03:31 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id WAA15803 for current-outgoing; Tue, 21 May 1996 22:03:31 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id WAA15796 for ; Tue, 21 May 1996 22:03:26 -0700 (PDT) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA02201; Wed, 22 May 1996 14:47:05 +0930 From: Michael Smith Message-Id: <199605220517.OAA02201@genesis.atrad.adelaide.edu.au> Subject: Re: bad keyboard reset routine? To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 22 May 1996 14:47:04 +0930 (CST) Cc: freebsd-current@freebsd.org In-Reply-To: <199605212308.BAA11211@uriah.heep.sax.de> from "J Wunsch" at May 22, 96 01:08:12 am 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 J Wunsch stands accused of saying: > > As Jordan K. Hubbard wrote: > > > Thanks for reminding me.. I also meant to mention that I've been > > getting: > > > > scprobe: keyboard RESET failed (result = 0xfa) > > Interesting. :-) > > I vote for killing scprobe()'s keyboard reset attempt entirely. It's > of no real use. Given that it will have reset on power-up, and the BIOS will have reset it again at least twice. It might be nice to make it an option depending on a 'flags' setting just in case someone needs it. > cheers, J"org -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] Collector of old Unix hardware. "Where are your PEZ?" The Tick [[