Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Nov 2009 11:42:30 +0100
From:      Matthias Reyelt <Matthias.Reyelt@brunel.de>
To:        Rafal Jaworowski <raj@semihalf.com>
Cc:        freebsd-arm@freebsd.org
Subject:   Re: Marvell Kirkwood 6281 mge1 interface
Message-ID:  <200911041142.32349.Matthias.Reyelt@brunel.de>
In-Reply-To: <B3FCAEF8-D564-4782-9490-73C7B97676FD@semihalf.com>
References:  <200911040956.09749.Matthias.Reyelt@brunel.de> <B3FCAEF8-D564-4782-9490-73C7B97676FD@semihalf.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,

here is the boot log. I have added several device_printf's and removed the 
0xffff condition in mii_phy_probe()

Matthias

ge0: <Marvell Gigabit Ethernet controller> at mem 0xf1072000-0xf1073fff irq 
12,13,14,11,46 on mbus0
mge0: bpf attached
mge0: Ethernet address: 00:50:43:01:a2:5e
mge0: Now probing PHY
mge0: mii_phy_probe: Starting to probe PHYs: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 
8:31085 ok
miibus0: (miibus_probe) is the mii device
mge0: (miibus_probe) is the eth device
miibus0: Probing phy 0 miibus0: No phy found
miibus0: Probing phy 1 miibus0: No phy found
miibus0: Probing phy 2 miibus0: No phy found
miibus0: Probing phy 3 miibus0: No phy found
miibus0: Probing phy 4 miibus0: No phy found
miibus0: Probing phy 5 miibus0: No phy found
miibus0: Probing phy 6 miibus0: No phy found
miibus0: Probing phy 7 miibus0: No phy found
miibus0: Probing phy 8 miibus0: found one. Now looking for ID
miibus0: Probing phy 9 miibus0: No phy found
miibus0: Probing phy a miibus0: No phy found
miibus0: Probing phy b miibus0: No phy found
miibus0: Probing phy c miibus0: No phy found
miibus0: Probing phy d miibus0: No phy found
miibus0: Probing phy e miibus0: No phy found
miibus0: Probing phy f miibus0: No phy found
miibus0: Probing phy 10 miibus0: No phy found
miibus0: Probing phy 11 miibus0: No phy found
miibus0: Probing phy 12 miibus0: No phy found
miibus0: Probing phy 13 miibus0: No phy found
miibus0: Probing phy 14 miibus0: No phy found
miibus0: Probing phy 15 miibus0: No phy found
miibus0: Probing phy 16 miibus0: No phy found
miibus0: Probing phy 17 miibus0: No phy found
miibus0: Probing phy 18 miibus0: No phy found
miibus0: Probing phy 19 miibus0: No phy found
miibus0: Probing phy 1a miibus0: No phy found
miibus0: Probing phy 1b miibus0: No phy found
miibus0: Probing phy 1c miibus0: No phy found
miibus0: Probing phy 1d miibus0: No phy found
miibus0: Probing phy 1e miibus0: No phy found
miibus0: Probing phy 1f miibus0: No phy found
miibus0: <MII bus> on mge0
miibus0: miibus_attach
e1000phy0: Probing e1000 PHY
e1000phy0: Probing e1000 PHY
e1000phy0: <Marvell 88E1116R Gigabit PHY> PHY 8 on miibus0
mge0: Writing 6800 to reg 10 on phy 8
mge0: Writing 70 to reg 14 on phy 8
mge0: Writing 9140 to reg 0 on phy 8
e1000phy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
mge0: [MPSAFE]
mge0: [ITHREAD]
mge0: [MPSAFE]
mge0: [ITHREAD]
mge1: <Marvell Gigabit Ethernet controller> at mem 0xf1076000-0xf1077fff irq 
16,17,18,15,46 on mbus0
mge1: bpf attached
mge1: Ethernet address: 00:50:43:01:a2:5f
mge1: Now probing PHY
mge1: mii_phy_probe: Starting to probe PHYs: 0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0 
8:0 9:65535 ok
miibus1: (miibus_probe) is the mii device
mge1: (miibus_probe) is the eth device
miibus1: Probing phy 0 miibus1: No phy found
miibus1: Probing phy 1 miibus1: No phy found
miibus1: Probing phy 2 miibus1: No phy found
miibus1: Probing phy 3 miibus1: No phy found
miibus1: Probing phy 4 miibus1: No phy found
miibus1: Probing phy 5 miibus1: No phy found
miibus1: Probing phy 6 miibus1: No phy found
miibus1: Probing phy 7 miibus1: No phy found
miibus1: Probing phy 8 miibus1: No phy found
miibus1: Probing phy 9 miibus1: found one. Now looking for ID
miibus1: Probing phy a miibus1: No phy found
miibus1: Probing phy b miibus1: No phy found
miibus1: Probing phy c miibus1: No phy found
miibus1: Probing phy d miibus1: No phy found
miibus1: Probing phy e miibus1: No phy found
miibus1: Probing phy f miibus1: No phy found
miibus1: Probing phy 10 miibus1: No phy found
miibus1: Probing phy 11 miibus1: No phy found
miibus1: Probing phy 12 miibus1: No phy found
miibus1: Probing phy 13 miibus1: No phy found
miibus1: Probing phy 14 miibus1: No phy found
miibus1: Probing phy 15 miibus1: No phy found
miibus1: Probing phy 16 miibus1: No phy found
miibus1: Probing phy 17 miibus1: No phy found
miibus1: Probing phy 18 miibus1: No phy found
miibus1: Probing phy 19 miibus1: No phy found
miibus1: Probing phy 1a miibus1: No phy found
miibus1: Probing phy 1b miibus1: No phy found
miibus1: Probing phy 1c miibus1: No phy found
miibus1: Probing phy 1d miibus1: No phy found
miibus1: Probing phy 1e miibus1: No phy found
miibus1: Probing phy 1f miibus1: No phy found
miibus1: <MII bus> on mge1
miibus1: miibus_attach
e1000phy1: Probing e1000 PHY
ukphy0: <Generic IEEE 802.3u media interface> PHY 9 on miibus1
ukphy0: OUI 0x3fffff, model 0x003f, rev. 15
mge1: Writing 8400 to reg 0 on phy 9
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 100baseT4, 
1000baseSX, 1000baseSX-FDX, 1000baseT, 1000baseT-FDX, auto
mge1: [MPSAFE]                                                                                                                                           


Am Mittwoch 04 November 2009 10:37:52 schrieb Rafal Jaworowski:
> 
> On 2009-11-04, at 09:56, Matthias Reyelt wrote:
> 
> > I have tried to use the second network interface on an Marvell  
> > OpenRD board
> > with BETA3. The mge1 interfaces seems to have problems with it's phy.
> >
> > I am not familiar with kernel debugging, I've only seen that  
> > mii_phy_probe()
> > detects the bmsr register at 0x09, but readreg returns 0xffff.
> >
> > Has anybody got that second interface up already?
> 
> Please paste the log with errors you're seeing.
> 
> Rafal
> 
> 




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200911041142.32349.Matthias.Reyelt>