Subject: Re: Intel Gigabit driver wm(4) fiber phy
To: None <tech-net@NetBSD.org>
From: Dheeraj S <dheeraj@ece.gatech.edu>
List: tech-net
Date: 09/12/2005 08:01:18
On Mon, Sep 12, 2005 at 01:39:28AM -0400, Allen Briggs wrote:
> On Sun, Sep 11, 2005 at 03:00:11PM +0000, Matthias Scheler wrote:
> > > wm0 at pci3 dev 7 function 0: Intel i82546EB 1000BASE-T Ethernet, rev. 1
> > > wm0: interrupting at irq 9
> > > wm0: 64-bit 33MHz PCI bus
> > > wm0: 256 word (8 address bits) MicroWire EEPROM
> > > wm0: Ethernet address 00:07:e9:05:7e:02
> > > makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
> > > makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
> >
> > This one is fine.
>
> That one's not fiber.
>
> > > wm2 at pci3 dev 8 function 0: Intel i82542 1000BASE-X Ethernet, rev. 3
> > > wm2: interrupting at irq 9
> > > wm2: 64 word (6 address bits) MicroWire EEPROM
> > > wm2: Ethernet address 00:d0:b7:45:7b:47
> > > wm2: 1000baseSX, 1000baseSX-FDX, auto
> >
> > It doesn't detect the PHY on this one. I guess there's a bug in the
> > wm(4) driver which causes this.
>
> There is a bug, but it's not a missing PHY. It detects the media--I
> presume that's done correctly. But it's not quite doing the right
> thing. I've heard reports from at least one other person that note
> the same behavior.
>
> -allen
>
> --
> Use NetBSD! http://www.NetBSD.org/
I have since then used the em driver in FreeBSD.(It comes from Intel), and it
works very nicely indeed. It seems to be way too different from the NetBSD
one. It doesn't even use any mii phy driver at all. Can we import that driver ?
truly
dheeraj
--
"Nature wants us to react, return blow for blow, cheating for cheating, lie for
lie, and then it requires a Divine power not to hit-back, keep control and
remain unattached, and act with prudence."