Call for Marvell/SysKonnect Yukon II Gigabit Ethernet testers.
Pyun YongHyeon
pyunyh at gmail.com
Wed Dec 13 04:33:26 PST 2006
On Wed, Dec 13, 2006 at 04:21:29AM -0500, Andre Guibert de Bruet wrote:
>
> On Wed, 13 Dec 2006, Pyun YongHyeon wrote:
>
> >On Wed, Dec 13, 2006 at 02:35:43AM -0500, Andre Guibert de Bruet wrote:
> >
> >> Sorry for the late reply. This is the output, including your latest
> >> round of changes (As committed):
> >>
> >> dmesg:
> >>
> >> mskc0: <Marvell Yukon 88E8050 Gigabit Ethernet> port 0xd800-0xd8ff mem
> >> 0xfcffc000-0xfcffffff irq 16 at device 0.0 on pci6
> >> mskc0: [FAST]
> >> msk0: <Marvell Technology Group Ltd. Yukon EC Id 0xb6 Rev 0x01> on mskc0
> >> msk0: Ethernet address: 00:04:23:b0:d2:cf
> >> miibus0: <MII bus> on msk0
> >> ukphy0: <Generic IEEE 802.3u media interface> on miibus0
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >> ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> >> 1000baseT-FDX, auto
> >
> >Hmm, it seems that e1000phy(4) failed to attach your PHY.
> >I'd like to know your PHY model/revision number.(You can set
> >bootverbose option and ukphy(4) will show OUI/model/revision
> >for your PHY.) With ukphy(4) you wouldn't get auto-crossover
> >feature or manual media selection work.
>
> I guess it looks better when I enable e1000phy (I was testing a dc-based
> card for a bit and forgot to re-enable it).
>
> mskc0: <Marvell Yukon 88E8050 Gigabit Ethernet> port 0xd800-0xd8ff mem
> 0xfcffc000-0xfcffffff irq 16 at device 0.0 on pci6
> mskc0: MSI count : 2
> mskc0: Reserved 0x4000 bytes for rid 0x10 type 3 at 0xfcffc000
> mskc0: RAM buffer size : 48KB
> mskc0: Port 0 : Rx Queue 32KB(0x00000000:0x00007fff)
> mskc0: Port 0 : Tx Queue 16KB(0x00008000:0x0000bfff)
> msk0: <Marvell Technology Group Ltd. Yukon EC Id 0xb6 Rev 0x01> on mskc0
> msk0: bpf attached
> msk0: Ethernet address: 00:04:23:b0:d2:cf
> miibus0: <MII bus> on msk0
> e1000phy0: <Marvell 88E1111 Gigabit PHY> on miibus0
> e1000phy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
> auto
Looks good. That 88E1111 was what I want to see.
>
> Do you still need the information for this PHY? boot -v doesn't seem to
No.
> provide this information when e1000phy is attached (It may be a good idea
Because e1000phy(4) was used for the PHY there is no output for
OUI/model/revision(e1000phy(4) already printed it anyway).
> print this information out for debugging, anyway).
>
> Andy
--
Regards,
Pyun YongHyeon
More information about the freebsd-current
mailing list