From: Jerry Van Baren <gerald.vanbaren@ge.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] TSEC/PHY @ MPC834x stopped working
Date: Wed, 02 Jul 2008 11:41:31 -0400 [thread overview]
Message-ID: <486BA1AB.8050202@ge.com> (raw)
In-Reply-To: <20080702103152.365f63fe.kim.phillips@freescale.com>
Kim Phillips wrote:
> On Wed, 02 Jul 2008 16:36:11 +0200
> Andre Schwarz <andre.schwarz@matrix-vision.de> wrote:
>
>> Ben,
>>
>> thanks for your quick reply.
>> Looks like you're right - nothing changed regarding network yet.
>>
>> Maybe it's a cpu specific problem.
>> Kim ? Can you help here ?
>>
>
> I know of nothing (barring this being the ETHADDR not specified
> problem) that could have caused this. Can you try using git-bisect?
>
> Kim
Some people were caught by the somewhat recent requirement for an
/aliases node and properties pointing to the "real" ethernet node (which
is a Good Thing[tm] because it makes the code board agnostic, pushes the
board configuration into the .dts where it belongs).
I don't associate Andre's assertion:
> Obviously the MII interface stopped working, i.e. all reads give 0xFF.
with the symptoms caused by a missing /aliases node. Maybe, maybe not,
could be my lack of experience.
Best regards,
gvb
next prev parent reply other threads:[~2008-07-02 15:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 14:03 [U-Boot-Users] TSEC/PHY @ MPC834x stopped working Andre Schwarz
2008-07-02 14:22 ` Ben Warren
2008-07-02 14:36 ` Andre Schwarz
2008-07-02 15:31 ` Kim Phillips
2008-07-02 15:41 ` Jerry Van Baren [this message]
2008-07-02 16:05 ` Andre Schwarz
2008-07-02 16:14 ` Jerry Van Baren
2008-07-02 16:01 ` Andre Schwarz
2008-07-02 16:32 ` Kim Phillips
2008-07-02 16:45 ` Andre Schwarz
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=486BA1AB.8050202@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.