In article <470FFBEF.6020000@dokein.co.uk>,
   Chris Gilbert <chris@dokein.co.uk> wrote:
> Izumi Tsutsui wrote:
> > chris@dokein.co.uk wrote:
> > 
> >> It's probably one of those that de works fine with but tlp doesn't (note
> >> if the card is in an i386 server it does work with the tlp driver)
> > 
> > FYI, I used tlp0 on cats for long time:
> >
> > tlp0 at pci0 dev 9 function 0: DECchip 21140A Ethernet, pass 2.0
> > tlp0: broken MicroWire interface detected; setting SROM size to 1Kb
> > tlp0: interrupting at irq 8
> > tlp0: Ethernet address 00:00:c0:ee:e4:f8
> > nsphy0 at tlp0 phy 3: DP83840 10/100 media interface, rev. 0
> > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

> I'm not sure which cards have the problem, but it happens with one of my
> tlps, but not the other.  The symptom is always that tlp doesn't find
> the phy.

> Normally with messages like:
> tlp0: unable to configure MII
> tlp0: no media found!

> There are emails about this going back to 2003.

> However my recent findings are that this issue doesn't happen in the
> chris-arm-intr-rework branch.  I believe the issue is MD, and related to
> how interrupts and spls work on cats.

I put a Linksys Ethernet card that I have in my Cats and that
works fine with NetBSD 4.0. dmesg says:

tlp0 at pci0 dev 9 function 0: ADMtek AN985 Ethernet, pass 1.1
tlp0: interrupting at irq 8
tlp0: Ethernet address 00:18:f8:0e:cd:0e
ukphy0 at tlp0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x00e092, model 0x0001, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

I guess the fact that the card is identified as 'tlp0' means
that it is using the 'tlp' driver for it. I do not know if this
helps investigate the problem. The Linksys card is a
LNE100TX-UK.

> Thanks,
> Chris

Dave Daniels