From owner-freebsd-current Sat Apr 15 00:06:11 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id AAA02250 for current-outgoing; Sat, 15 Apr 1995 00:06:11 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id AAA02240 for ; Sat, 15 Apr 1995 00:06:07 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id AAA03505 for freebsd-current@FreeBSD.org; Sat, 15 Apr 1995 00:03:32 -0700 From: "Rodney W. Grimes" Message-Id: <199504150703.AAA03505@gndrsh.aac.dev.com> Subject: Re: Interesting (and odd) effect in -current To: freebsd-current@FreeBSD.org Date: Sat, 15 Apr 1995 00:03:31 -0700 (PDT) In-Reply-To: <199504150643.IAA01868@uriah.heep.sax.de> from "J Wunsch" at Apr 15, 95 08:43:04 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 744 Sender: current-owner@FreeBSD.org Precedence: bulk > > As Rodney W. Grimes wrote: > > > > > Wouldn't it be a good idea in general if we zero all of the RAM in locore.s > > > IMHO, no, this should have already been done by the BIOS at power up > > time. > > But the BIOS doesn't do it for a warm boot, does it? Some do, that is why we sometimes loose the msgbuf on a reboot, some don't. But either way you only have to initialize memory once after power on, as once you do that parity should stay consistent, as nothing turns off the parity generators. Infact a lot of chip sets don't even have a bit to turn this on and off :-). -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Custom computers for FreeBSD