From owner-cvs-all Mon Aug 14 11:11:14 2000 Delivered-To: cvs-all@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 3357937BF0F; Mon, 14 Aug 2000 11:11:00 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.14 #2) id 13OOhD-0006hk-00; Mon, 14 Aug 2000 18:10:47 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.9.3/8.9.3) id TAA01452; Mon, 14 Aug 2000 19:36:37 +0200 (CEST) (envelope-from wkb) Date: Mon, 14 Aug 2000 19:36:37 +0200 From: Wilko Bulte To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: John Hay , Peter Wemm , cvs-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/release/scripts dokern.sh Message-ID: <20000814193637.D1401@freebie.demon.nl> References: <20000813232620.A907@freebie.demon.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from groudier@club-internet.fr on Mon, Aug 14, 2000 at 12:37:24AM +0200 X-OS: FreeBSD 4.1-STABLE X-PGP: finger wilko@freebsd.org Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by freebie.demon.nl id TAA01452 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 14, 2000 at 12:37:24AM +0200, G=E9rard Roudier wrote: >=20 > On Sun, 13 Aug 2000, Wilko Bulte wrote: >=20 > > On Sun, Aug 13, 2000 at 07:45:30PM +0200, G=E9rard Roudier wrote: ... > Having PCI parity errors silently ignored seems far less critical with > Network devices as long as a CRC is checked by software. With PCI-SCSI > controllers we don't have such a software CRC. I see. Unfortunately it seems to be All or Nothing as far as the SRM cons= ole option is concerned. > > I don't remember ever having seen this requirement for the ncr/sym 81= 0s > > though. >=20 > I don't remember ever having seen a ncr/sym device that comes from boot > with PCI parity error signaling enabled in the PCI COMMAND register. > Neither I have ever seen any other driver for these devices being caref= ul > about really enabling PCI parity error checking and reporting. This may > explain that. >=20 > Is there some way for the driver to know about the hardware PCI parity > brokenness? Not that I know. I can try to dig up what card types / brands need the=20 PCI parity disable on Alpha. Maybe you see a pattern there? --=20 Wilko Bulte wilko@freebsd.org Arnhem, the Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message