From owner-freebsd-current  Fri Apr 14 19:05:02 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id TAA21881
          for current-outgoing; Fri, 14 Apr 1995 19:05:02 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA21869
          for <current@freebsd.org>; Fri, 14 Apr 1995 19:04:50 -0700
Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id TAA18271; Fri, 14 Apr 1995 19:04:43 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id TAA00579; Fri, 14 Apr 1995 19:04:43 -0700
Message-Id: <199504150204.TAA00579@corbin.Root.COM>
To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>
cc: phk@ref.tfs.com (Poul-Henning Kamp), cmf@ins.infonet.net,
        current@FreeBSD.org
Subject: Re: Interesting (and odd) effect in -current 
In-reply-to: Your message of "Fri, 14 Apr 95 18:06:32 PDT."
             <199504150106.SAA02129@gndrsh.aac.dev.com> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 14 Apr 1995 19:04:43 -0700
Sender: current-owner@FreeBSD.org
Precedence: bulk

>But I have digressed, if the BIOS didn't manage to get this write at
>power on, you would get NMI interrupts no matter what OS you ran.  I
>don't see a reason to add code to FreeBSD that really belongs in the
>BIOS in the off chance that some really rare broken motherboard could
>then work.

   I agree, but I think clearing memory has other merits.

-DG