From owner-aic7xxx Wed Jul 29 13:43:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23613 for aic7xxx-outgoing; Wed, 29 Jul 1998 13:43:32 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from slave2.aa.net (slave2.aa.net [204.157.220.251]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23603 for ; Wed, 29 Jul 1998 13:43:18 -0700 (PDT) (envelope-from proverbs@wolfenet.com) Received: from omlet (omlet.pirih.aa.net [204.137.133.139]) by slave2.aa.net (8.9.0.Beta3/8.8.5) with SMTP id NAA14136 for ; Wed, 29 Jul 1998 13:42:45 -0700 X-Intended-For: Message-Id: <3.0.5.32.19980729134413.0098e800@popserv.wolfenet.com> X-Sender: proverbs@popserv.wolfenet.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 29 Jul 1998 13:44:13 -0700 To: aic7xxx Mailing List From: Chris Pirih Subject: Re: Puzzle for Doug... In-Reply-To: References: <35BE5247.16EC040F@dialnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 11:27 AM 07/29/1998 -0400, Robert G. Brown wrote: >What if the memory was remapped to a nonexistent location? You write >to the location and there is nothing there. You read from the >location and get nulls -- obviously a parity violation but now >remapped to a location where the error comes up as NMI. I like that theory! There doesn't even have to be a write, just a read -- machines without parity/ECC memory would return 0xFF... or whatever, and machines with parity/ECC would NMI. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message