From owner-freebsd-current@FreeBSD.ORG  Thu Jan  8 13:11:06 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 9E61616A4CE
	for <current@FreeBSD.org>; Thu,  8 Jan 2004 13:11:06 -0800 (PST)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5A26E43D53
	for <current@FreeBSD.org>; Thu,  8 Jan 2004 13:11:04 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
	by gw.catspoiler.org (8.12.9p2/8.12.9) with ESMTP id i08LAv7E020805
	for <current@freebsd.org>; Thu, 8 Jan 2004 13:11:01 -0800 (PST)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200401082111.i08LAv7E020805@gw.catspoiler.org>
Date: Thu, 8 Jan 2004 13:10:57 -0800 (PST)
From: Don Lewis <truckman@FreeBSD.org>
To: current@FreeBSD.org
In-Reply-To: <200401071932.i07JWN7E017376@gw.catspoiler.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Subject: Re: Call for testers - dc ethernet driver patch
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jan 2004 21:11:06 -0000

On  7 Jan, Don Lewis wrote:
> The dc driver has been broken ever since it was converted to use busdma.
> The symptoms are that it reports spurious output errors and collisions,
> even when running in full-duplex mode.  I believe the patch below fixes
> the problem, but I do not have the appropriate hardware to test it.  I
> have had one gotten one report so far from someone who claims this patch
> fixed the problems he was seeing.  I'd appreciate further testing of
> this patch, especially with as many of the chipsets supported by the
> driver as possible so that I can commit this patch.  Please mention the
> type of hardware you are using (machine architecture and card probe
> message) in your reports. This is somewhat time critical because I've
> had users express interest in getting this into 5.2.

Thanks to everyone who has sent me testing results.  The results have
been universally good so I committed the patch.  It will probably be
MFC'ed to 5.2 in about 23 hours.