From owner-freebsd-net@FreeBSD.ORG  Mon May 26 17:51:45 2008
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 1948C106566C;
	Mon, 26 May 2008 17:51:45 +0000 (UTC) (envelope-from wjw@digiware.nl)
Received: from mail.digiware.nl (www.tegenbosch28.nl [217.21.251.97])
	by mx1.freebsd.org (Postfix) with ESMTP id B589C8FC1C;
	Mon, 26 May 2008 17:51:44 +0000 (UTC) (envelope-from wjw@digiware.nl)
Received: from localhost (localhost.digiware.nl [127.0.0.1])
	by mail.digiware.nl (Postfix) with ESMTP id 11C0E17394;
	Mon, 26 May 2008 19:21:30 +0200 (CEST)
X-Virus-Scanned: amavisd-new at digiware.nl
Received: from mail.digiware.nl ([127.0.0.1])
	by localhost (rack1.digiware.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id lg+ou8gvjXwu; Mon, 26 May 2008 19:21:25 +0200 (CEST)
Received: from [192.168.2.10] (unknown [192.168.2.10])
	by mail.digiware.nl (Postfix) with ESMTP id 285D31738B;
	Mon, 26 May 2008 19:21:24 +0200 (CEST)
Message-ID: <483AF194.2020002@digiware.nl>
Date: Mon, 26 May 2008 19:21:24 +0200
From: Willem Jan Withagen <wjw@digiware.nl>
Organization: Digiware
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: Steve Kargl <sgk@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>
In-Reply-To: <20080526163844.GA37636@troutmask.apl.washington.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 26 May 2008 17:51:45 -0000

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