From owner-aic7xxx Thu Jul 30 05:43:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01041 for aic7xxx-outgoing; Thu, 30 Jul 1998 05:43:41 -0700 (PDT) (envelope-from owner-aic7xxx@FreeBSD.ORG) Received: from smtp.enteract.com (thor.enteract.com [206.54.252.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA01027 for ; Thu, 30 Jul 1998 05:43:37 -0700 (PDT) (envelope-from isely@enteract.com) Received: (qmail 11291 invoked from network); 30 Jul 1998 12:43:35 -0000 Received: from nathan.enteract.com (isely@207.229.129.3) by thor.enteract.com with SMTP; 30 Jul 1998 12:43:35 -0000 Date: Thu, 30 Jul 1998 07:43:46 -0500 (CDT) From: Mike Isely Reply-To: Mike Isely To: Doug Ledford cc: Mike Isely , Chris Pirih , aic7xxx Mailing List , rgb@phy.duke.edu Subject: Re: Puzzle for Doug... In-Reply-To: <35C02F51.AE4D577C@dialnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-aic7xxx@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 30 Jul 1998, Doug Ledford wrote: > Mike Isely wrote: > > > Note that in order for this theory to be right, such an access has to get > > past the system's page tables first. > > Which should never happen and is outside the control of the aic7xxx driver > anyway. Except page mapping (on x86 at least) has a 4KB granularity. Are memory-mapped PCI devices required to address-decode the entire 4KB? Or does that chipset "know" that such a 4KB block is all "device" and therefore doesn't try to parity-check any of it? Perhaps the aic7xxx software is accessing a device register which happens to not exist on the aic7890. Well that's probably a stretch. I'll be quiet now... | Mike Isely | PGP fingerprint POSITIVELY NO | | 03 54 43 4D 75 E5 CC 92 UNSOLICITED JUNK MAIL! | isely @ pobox (dot) com | 71 16 01 E2 B5 F5 C1 E8 | (spam-foiling address) | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe aic7xxx" in the body of the message