linux-mips
[Top] [All Lists]

Re: Help with BCM7038 Ethernet driver

To: Scott S <techtom@netzero.net>
Subject: Re: Help with BCM7038 Ethernet driver
From: "Steven J. Hill" <sjhill@realitydiluted.com>
Date: Wed, 18 Jul 2007 07:50:26 -0500
Cc: linux-mips@linux-mips.org
In-reply-to: <5.1.0.14.2.20070718023126.0367b5f0@unixmail.qualcomm.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <5.1.0.14.2.20070718023126.0367b5f0@unixmail.qualcomm.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.13 (2006-08-11)
> I verified with Ethereal, the ethernet driver can send packets, but the 
> 7038 acts as if interrupts are disabled.  I verified that interrupt 23 is 
> enabled, but no interrupts occur.  The uart and the ide/sata interface work 
> fine, so the MIPS int 2 is working fine.  I know there is nothing wrong 
> with the ethernet interface because I use it to boot the kernel in CFE. 
> (see boot below)
> 
Typically this type of behavior has to do with the PHY. If you can send
packets, but not receive....you're PHY is in half-duplex and something
went wrong with autonegotation. Broadcom, AMD, Marvell and others almost
always have some software work arounds for PHY bugs. Did you look up
the part number for the PHY used on your board and grep through the net
drivers in the Linux kernel for possible work-arounds done by some of
the other network drivers? I do not know if your version of CFE has the
ability to examine the PHY registers. If so, do a 'ifconfig /auto' to
get your IP address for your board. Then dump the PHY registers. Next,
boot your kernel and dump the PHY registers and look at differences.

-Steve

<Prev in Thread] Current Thread [Next in Thread>