Re: kern/39094 (Add et (Agere ET1310/ET1301) network driver to NetBSD)

[Kaspar Brand <netbsd+gnats%velox.ch@localhost>]

The following reply was made to PR kern/39094; it has been noted by GNATS.

From: Kaspar Brand <netbsd+gnats%velox.ch@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: jnemeth%NetBSD.org@localhost
Subject: Re: kern/39094 (Add et (Agere ET1310/ET1301) network driver to NetBSD)
Date: Mon, 05 Jan 2009 19:12:13 +0100

 Ok, I've tested ET-i386 in the meantime, i.e.:
 
 NetBSD 5.99.5 (ET) #0: Wed Dec 31 10:56:30 PST 2008
        
jnemeth@P4-3679GHz:/usr/local/NetBSD-current/i386-objdir/sys/arch/i386/compile/ET
 
 everything was properly detected:
 
 et0 at pci1 dev 0 function 0: Lucent Technologies ET1310 10/100/1000 Ethernet 
(rev. 0x01)
 et0: interrupting at ioapic0 pin 16
 et0: Ethernet address 00:0a:9d:09:2f:52
 etphy0 at et0 phy 0: Agere ET1011 10/100/1000baseT PHY, rev. 2
 etphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT-FDX, auto
 
 and a couple of traffic tests (mainly with ttcp) also worked to
 my satisfaction - so yes, I think it's ready for being committed.
 
 As an additional data point, note that I have been running a
 patched NetBSD 4.0 kernel with this driver for several months
 by now, and didn't experience any problems so far.
 
 Finally, a last thing to note: I changed the device ID for the
 ET1301 controller on purpose - according to the data sheet, it's
 0xed01, not 0xed0a (as in the DragonFly/OpenBSD sources). I can't
 verify with a real controller, however, since I only have a system
 with an ET1310.