> btw, is the elink3.c code fixed yet?  my ep0's behaving strangely
> after I put my machine back at school... something's wrong...

 
> Aug 23 05:47:35 andrewbert /netbsd: ep0 at pci0 dev 15 function 0: 3Co
>m 3C590
>  Ethernet
> Aug 23 05:47:35 andrewbert /netbsd: ep0: MAC address 00:a0:24:c0:ee:af
> Aug 23 05:47:35 andrewbert /netbsd: ep0: 8KB byte-wide FIFO, 1:1 Rx:Tx split,
>  utp/aui/bnc default utp
> Aug 23 05:47:35 andrewbert /netbsd: ep0: interrupting at irq 10 


> Aug 23 05:47:36 andrewbert /netbsd: ep0:  read 0x10, 0x2 from EP_W3_CONFIG re
> gister
> Aug 23 05:47:36 andrewbert /netbsd: epsetmedia: ep0: medium 0x0, 0x2 t
>o EP_W3
> _CONFIG
> Aug 23 05:47:36 andrewbert /netbsd: ep0:  read 0x10, 0x2 from EP_W3_CONFIG re
> gister
> Aug 23 05:47:36 andrewbert /netbsd: epsetmedia: ep0: medium 0x0, 0x2 to EP_W3
> _CONFIG

Ah, you have DEBUG turned on in your kernel config.  The if_ep driver
logs extra information about media changes when DEBUG is on.  The
logging is there because, AFAIK, the driver hasn't ever been tried
with 100-T4 cards.  This has nothing whatever to do with the known
compiler problems with elink3.c

I'm assuming your card works. Is that right?