From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Problems with new ethernet init on mpc8360
Date: Tue, 26 Feb 2008 15:30:16 -0500 [thread overview]
Message-ID: <47C476D8.7040905@ge.com> (raw)
In-Reply-To: <01bd01c878b1$91e57e20$b5b07a60$@Tjernlund@transmode.se>
Joakim Tjernlund wrote:
[snip]
> Maybe you suffer from something I noticed, sometimes the master for MDIO gets
> out of sync. Try this patch and see if it helps, not sure if it still applies
> but that should be easy to fix up.
It applied cleanly with some line offsets, but didn't fix my problem. :-(
> From 241d7e4f4fb26b2424311a6012c845bd97dfdafa Mon Sep 17 00:00:00 2001
> From: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
> Date: Tue, 18 Dec 2007 14:33:18 +0100
> Subject: [PATCH] Move call to qe_set_mii_clk_src() into uec_read_phy_reg() and
> uec_write_phy_reg() to make sure MII master clock source is
> correct.
>
> ---
> drivers/qe/uec.c | 5 -----
> drivers/qe/uec_phy.c | 6 ++++++
> 2 files changed, 6 insertions(+), 5 deletions(-)
Defining the netmask didn't help either. Since it works the first time,
including bootp with a full tftp load (lots of packets), it implies the
network is fine but someone is shutting down the network (improperly?)
after the ping/tftp/bootp command completes and not starting it up again
on the next network command.
Thanks,
gvb
prev parent reply other threads:[~2008-02-26 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 3:55 [U-Boot-Users] Problems with new ethernet init on mpc8360 Jerry Van Baren
2008-02-26 17:07 ` Kim Phillips
2008-02-26 17:31 ` Jerry Van Baren
2008-02-26 18:01 ` Jerry Van Baren
2008-02-26 18:30 ` Jerry Van Baren
2008-02-26 18:40 ` Jerry Van Baren
2008-02-26 19:55 ` Joakim Tjernlund
2008-02-26 20:04 ` Joakim Tjernlund
2008-02-26 20:30 ` Jerry Van Baren [this message]
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=47C476D8.7040905@ge.com \
--to=gerald.vanbaren@ge.com \
--cc=u-boot@lists.denx.de \
/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