> On Mon, 24 Feb 2003 18:13:42 -0800 (PST), in sentex.lists.freebsd.current
> you wrote:

> >be reliable, nevermind pleasant to look at. I only have access to
> >an 82550 card, so I don't know if this is fixed in the 82551 or not.
> 
> Hi,
> Can you tell reliably from the dmesg which type one has ?
> 
> % dmesg | egrep -i "fxp|inphy"
> fxp0: <Intel Pro 10/100B/100+ Ethernet> port 0xc000-0xc03f mem
> 0xe8800000-0xe881ffff,0xe8831000-0xe8831fff irq 11 at device 1.0 on pci1
> fxp0: Ethernet address 00:07:e9:09:69:60
> inphy0: <i82555 10/100 media interface> on miibus0
> inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> fxp1: <Intel Pro/100 Ethernet> port 0xc800-0xc83f mem 0xe8832000-0xe8832fff
> irq 10 at device 8.0 on pci1
> fxp1: Ethernet address 00:01:80:40:0e:b3
> inphy1: <i82562ET 10/100 media interface> on miibus1
> inphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
> 
> Or do you have to look at the card / MB ?

This is a good question. I apologize for not providing this info right
off the bat.

The fxp driver seems to use the same name strings for lots of different
cards, so dmesg won't help you identify it. The only way to tell you have
an 82550, other than looking at the card itself and checking for the
i82550 part number, is to do:

# pciconf -l | grep fxp

and check for a revision code of 0xc (12) or higher. if_fxpreg.h lists
a bunch of known revision values. Anything up to and including 0x9 is
an 82557/8/9, which won't gain anything from these mods, I'm sorry to
say.

-Bill

--
=============================================================================
-Bill Paul            (510) 749-2329 | Senior Engineer, Master of Unix-Fu
                 [EMAIL PROTECTED] | Wind River Systems
=============================================================================
      "If stupidity were a handicap, you'd have the best parking spot."
=============================================================================

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to