From owner-freebsd-hackers Wed Mar 4 11:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03046 for freebsd-hackers-outgoing; Wed, 4 Mar 1998 11:25:56 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA02953 for ; Wed, 4 Mar 1998 11:25:33 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: by uni4nn.gn.iaf.nl with UUCP id AA20914 (5.67b/IDA-1.5 for hackers@FreeBSD.ORG); Wed, 4 Mar 1998 20:24:08 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.7/8.6.12) id TAA01178; Wed, 4 Mar 1998 19:10:21 +0100 (MET) From: Wilko Bulte Message-Id: <199803041810.TAA01178@yedi.iaf.nl> Subject: Re: do you support In-Reply-To: <199803041510.IAA11577@pluto.plutotech.com> from "Justin T. Gibbs" at "Mar 4, 98 08:07:01 am" To: gibbs@plutotech.com (Justin T. Gibbs) Date: Wed, 4 Mar 1998 19:10:21 +0100 (MET) Cc: nate@mt.sri.com, gibbs@plutotech.com, tom@sdf.com, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL32 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Justin T. Gibbs wrote... > >> So why is it that the NCR driver works so well? I think this is > >> more a matter of perspective than fact. There are users of both > >> the Adaptec and NCR cards that will say they work flawlessly and > >> users who say they break in configuration X > > > >I don't know of any NCR users that have ever said it was broken. Either > >it worked, or it didn't. No corruptions, no weird error messages, if it > >was found it worked. > > > >Nate > > Read the NetBSD lists. There seem to be a lot of NetBSD users that have lotsa problems with the ncr. On my Alpha it works just fine. The 2 in my FreeBSD box also work fine. But be careful: it seems that the NetBSD problems are (highly) sensitive to the brand/model of devices attached to it. So it looks to me like a less than optimal behaviour of the driver when confronted with less-than-optimal firmware/devices. > Justin _ ______________________________________________________________________ | / o / / _ Bulte email: wilko @ yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' --------------- Support your local daemons: run [Free,Net,Open]BSD Unix -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message