From owner-freebsd-current  Mon Feb 19 13:53:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id NAA27345
          for current-outgoing; Mon, 19 Feb 1996 13:53:52 -0800 (PST)
Received: from nervosa.com (root@nervosa.com [192.187.228.86])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id NAA27335
          for <freebsd-current@FreeBSD.org>; Mon, 19 Feb 1996 13:53:45 -0800 (PST)
Received: from nervosa.com (coredump@onyx.nervosa.com [10.0.0.1]) by nervosa.com (8.7.3/nervosa.com.2) with SMTP id NAA00367; Mon, 19 Feb 1996 13:53:25 -0800 (PST)
Date: Mon, 19 Feb 1996 13:53:24 -0800 (PST)
From: invalid opcode <coredump@nervosa.com>
To: Søren Schmidt <sos@DeepCore.dk>
cc: HOSOKAWA Tatsumi <hosokawa@mt.cs.keio.ac.jp>, KentH@HNS.St-Louis.Mo.US,
        freebsd-current@FreeBSD.org
Subject: Re: Keyboard lockout on 2.x.x
In-Reply-To: <199602191957.UAA00474@DeepCore.dk>
Message-ID: <Pine.BSF.3.91.960219135240.207A-100000@nervosa.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Transfer-Encoding: QUOTED-PRINTABLE
Sender: owner-current@FreeBSD.org
Precedence: bulk

On Mon, 19 Feb 1996, S=F8ren Schmidt wrote:
> > Since I replaced all DELAY(10) with DELAY(100) in syscons.c, it never
> > happen.  But I'm not sure whether it's a good solution.
>=20
> I think it is actually more a hideaway of the symptoms, rather than
> a fix for the disease...
> S=F8ren Schmidt               (sos@FreeBSD.org)               FreeBSD Cor=
e Team

This might actually be to form a compatibility layer for faulty (slow?)=20
hardware.

=3D=3D Chris Layne  =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=3D=3D coredump@nervosa.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D http://www.nervosa.com/~coredump =3D=3D