Date: Mon, 26 May 2008 19:21:24 +0200 From: Willem Jan Withagen <wjw@digiware.nl> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: arch@freebsd.org, Robert Watson <rwatson@freebsd.org>, current@freebsd.org, Ade Lovett <ade@freebsd.org>, net@freebsd.org Subject: Re: HEAD UP: non-MPSAFE network drivers to be disabled Message-ID: <483AF194.2020002@digiware.nl> In-Reply-To: <20080526163844.GA37636@troutmask.apl.washington.edu> References: <20080524111715.T64552@fledge.watson.org> <1211640498.1510.8.camel@localhost> <20080524165519.K9809@fledge.watson.org> <e7db6d980805241656q30193933hcd983b6322d02df8@mail.gmail.com> <20080525105726.O39741@fledge.watson.org> <5D4AF8D7-88A7-4197-A0FE-7CA992EE5F96@FreeBSD.org> <20080526163844.GA37636@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Steve Kargl wrote: > On Mon, May 26, 2008 at 05:34:09AM -0700, Ade Lovett wrote: >> idiosyncratic situations (yes, ahc(4), I'm looking at you) for 5+ > > What's the problem with ahc(4)? My ahc controller is one of > the most reliable pieces of hardware that I've purchased. > It's also the only interface available to my external DLT > tape drive. Not to forget the large amount of embedded ahc's that got implemented on all kinds of serverbords. I still have quite a large set of customers with such ASUS boards I sold to them over the years. Up 'till now I've been able to keep 'm running with the pace of FreeBSD. Removing this driver would "leave them behind". I can force them to upgrade, but thus far there has been little reason for that (hardware wise). Just my 2 ct's --WjW
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?483AF194.2020002>