linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: "Steven A. Falco" <sfalco@harris.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Sequoia EMAC only works if u-boot initializes it?
Date: Mon, 26 Nov 2007 10:08:43 -0600	[thread overview]
Message-ID: <20071126100843.2ee3e0b9@weaponx> (raw)
In-Reply-To: <474AED67.4020006@harris.com>

On Mon, 26 Nov 2007 10:59:35 -0500
"Steven A. Falco" <sfalco@harris.com> wrote:

> I have noticed odd behavior on a Sequoia board.  Kernel is built from 
> DENX git, ARCH=powerpc, 2.6.23.1.
> 
> Sequence that works:
> 1) In u-boot, do "dhcp" (this initializes the PHY)
> 2) Boot linux from flash
> 3) ifconfig eth0 192.168.0.101 netmask 255.255.255.0 up
> Ethernet is now functional, and I can ping the Sequoia (and it can ping 
> my host)
> 
> Sequence that does not work:
> 1) Boot linux from flash without letting u-boot touch eth0
> 2) ifconfig eth0 192.168.0.101 netmask 255.255.255.0 up
> Ethernet appears to come up, but it is not functional.  I.e. I get 
> "eth0: link is up, 100 FDX, pause enabled" but I cannot ping the board, 
> and the board cannot ping my host.
> 
> So, the kernel appears to be missing some initialization that u-boot 
> provides.

There are some PHY patches from Valentine that Ben needs to send to
Jeff Garzik.

josh

  reply	other threads:[~2007-11-26 16:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-26 15:59 Sequoia EMAC only works if u-boot initializes it? Steven A. Falco
2007-11-26 16:08 ` Josh Boyer [this message]
2007-11-26 16:20 ` Stefan Roese
2007-11-26 19:10   ` Steven A. Falco
2007-11-26 20:08     ` Benjamin Herrenschmidt
2007-11-26 22:46       ` Steven A. Falco
2007-11-26 22:49         ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071126100843.2ee3e0b9@weaponx \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfalco@harris.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).