Tanmay Kishore
|
Re: RE: RE: RE: RE: BCM5709S
|
Tanmay Kishore
04/07/2009 6:02 PM
post26294
|
Re: RE: RE: RE: RE: BCM5709S
So, I could finally get to a stage where the 5709 driver can detect the SERDES PHY. But unfortunately, it compalins
about "no carrier" when I run the ifconfig command. In my log, I see the gentbi.c phy driver getting executed and it
detects the PHY device twice, once for phy address = 2, and the next one for phy address == 3. Here's the log:
gentbi2 at bnx2 phy 2: Generic ten-bit interface, rev. 0
gentbi2: 1000baseSX, 1000baseSX-FDX, auto
Find PHY, oui = 00000af7, model = 0000003f
gentbi3 at bnx2 phy 31: Generic ten-bit interface, rev. 0
gentbi3: 1000baseSX, 1000baseSX-FDX, auto
These logs are from mii.c:mii_attach() and gentbi.c:gentbiattach() function calls. The locations of the files is under
sys/dev/mii folder. What I am not able to understand is why the gentbiattach function executes twise for the same device
.
Secondly, the output of ifconfig shows no carrier detect under the status field. Here's the output:
>ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33192
inet 127.0.0.1 netmask 0xff000000
bnx0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0
address: 00:10:18:49:7b:d4
media: Ethernet autoselect
status: no carrier
inet 172.22.130.12 netmask 0xffffff00 broadcast 172.22.130.255
bnx2: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
capabilities=7<IP4CSUM,TCP4CSUM,UDP4CSUM>
enabled=0
address: 00:10:18:49:7b:d0
media: Ethernet autoselect
status: no carrier
As you can see, the status shows up as no carrier. Do you guys know what could be causing this? I can send you some
status register dumps if that helps. But you will have to ask specifically which dump are you interested in.
Thanks,
Tanmay
|
|
|