RE: Call for testers - dc ethernet driver patch

It resolved the spurious collisions on my machine(Fortunatelly, I don't have
output errors previously, and of course the patch didn't brought me any :P
). Is the following information enough?

# uname -a
FreeBSD beastie.frontfree.net 5.2-RC FreeBSD 5.2-RC #15: Thu Jan  8 04:26:11
CST 2004     delphij_at_beastie.frontfree.net:/usr/obj/usr/src/sys/BEASTIE
i386

# cat /var/run/dmesg.boot
dc0: <Macronix 98713 10/100BaseTX> port 0xe400-0xe4ff mem
0xe4400000-0xe44000ff irq 11 at device 9.0 on pci0
dc0: Ethernet address: 00:00:b4:74:8f:2c

# ifconfig
dc0: flags=18843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        (....address omitted here....)
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active  

Sincerely,
Xin LI,
Repomeister and Liaison,
The FreeBSD Simplified Chinese Project

> -----Original Message-----
> From: owner-freebsd-current_at_freebsd.org 
> [mailto:owner-freebsd-current_at_freebsd.org] On Behalf Of Don Lewis
> Sent: Thursday, January 08, 2004 3:32 AM
> To: current_at_FreeBSD.org
> Cc: re_at_FreeBSD.org
> Subject: Call for testers - dc ethernet driver patch
> 
> 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.