On Fri, Nov 28, 2003 at 08:32:55PM +0200, Arto Huusko wrote:
> Hi all,
> 
> ....
> tlp0 at pci0 dev 6 function 0: DECchip 21040 Ethernet, pass 2.4
> tlp0: interrupting at kn20aa irq 13
> tlp0: Ethernet address 00:00:f8:21:9d:b2
> tlp0: 10baseT, 10baseT-FDX, 10base5, manual
> tlp1 at pci0 dev 12 function 0: DECchip 21140 Ethernet, pass 1.2
> tlp1: interrupting at kn20aa irq 4
> tlp1: DEC DE500-XA, Ethernet address 00:00:f8:30:28:35
> tlp1: 10baseT, 100baseTX, 100baseTX-FDX, 10baseT-FDX
> 

> I was just wondering whether there might be any difference
> or advantage in using de driver or tlp? (Or might it be sensible
> to replace tlp1 with a spare rtk NIC?)
> 

I don't know about rtk NICs but I swapped most of my DE500s to these:

ex0 at pci0 dev 7 function 0: 3Com 3c905B-TX 10/100 Ethernet (rev. 0x64)
ex0: interrupting at kn20aa irq 8
ex0: MAC address 00:50:da:65:ee:6c
ukphy0 at ex0 phy 24: Generic IEEE 802.3u media interface

And they work just fine (w/ autoselect).  

I have one tlp that's been running with autoselect and FDX for a long time:

tlp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 08:00:2b:c3:2c:82
	media: Ethernet autoselect (100baseTX full-duplex)
	status: active

tlp1 at pci0 dev 7 function 0: DECchip 21143 Ethernet, pass 3.0
tlp1: interrupting at kn20aa irq 8
tlp1: DEC DE500-BA, Ethernet address 08:00:2b:c3:2c:82
tlp1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

(in case you're wondering, tlp0 is the built-in 10Base-T)

And I haven't seen any MII CRC errors with it. All are on 500/500s running
releases from 1.5-branch to -current.

-- 
jht