Bill Studenmund wrote:

> I think the tlp driver needs a kernel config option to match the 21041.
> Like options TLP_MATCH_21041 . This is so that you can have de's and tlp's
> in the same machine at the same time.

[Matt Thomas sent the very same info]

Thanks guys. I added the option and the kernel compiled and booted,
seemed to recognize the cards:

tlp0 at pci0 dev 13 function 0: DECchip 21041 Ethernet, pass 2.1        
       
tlp0: interrupting at irq 23                                            
       
tlp0: Ethernet address 00:80:19:44:3f:d9                                
       
tlp0: 10baseT, 10base2, 10baseT-FDX                                     
       
tlp0: supplying EUI64: 00:80:19:ff:fe:44:3f:d9                          
       
tlp1 at pci0 dev 14 function 0: DECchip 21041 Ethernet, pass 2.1        
       
tlp1: interrupting at irq 25                                            
       
tlp1: Ethernet address 00:80:19:44:3f:b5                                
       
tlp1: 10baseT, 10base2, 10baseT-FDX                         

tlp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500                  
       
        address: 00:80:19:44:3f:d9                                      
       
        media: Ethernet 10baseT                                         
       
        status: no carrier                                              
       
tlp1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500                  
       
        address: 00:80:19:44:3f:b5                                      
       
        media: Ethernet 10baseT                                         
       
        status: no carrier                           

tlp0 is the one connected to the hub at the moment. When I tried to
bring it up the machine drowned under a storm of 'error: buffer ring
overrun', every once in a while it would throw up something else but it
sped by too fast to read. I guess this is why the tlp driver isn't ready
for prime time.

cheers, 

Matthew