From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] PATCH: fix FEC problems on MPC5200
Date: Thu, 25 Mar 2004 10:17:53 +0100 [thread overview]
Message-ID: <4062A3C1.40107@staubli.com> (raw)
In-Reply-To: <20040325090301.4E844C0655@atlas.denx.de>
Wolfgang Denk wrote:
>In message <40629804.5060107@staubli.com> you wrote:
>
>
>>The attached patch fixes the FEC problems on my Lite5200 board. The network
>>is working without any problems at 10 and 100Mb. The auto-negociation
>>works too.
>>
>>If CONFIG_FEC_10MBIT is defined, the FEC works at 10Mb with Half-Duplex.
>>If CONFIG_FEC_10MBIT is undefined, the MII reads its configuration from
>>hardware
>>and uses the auto-negociation for determining network speed.
>>The patch undefines CONFIG_FEC_10MBIT for the Lite5200.
>>
>>Does it work for the other MPC5xxx boards ?
>>
>>
>
From what we saw, the FEC driver in U-Boot used to work quite stably,
>until the IDE support was added. May be that was just a coincidence,
>but it seems obvious to me that something changed in U-Boot recently
>that broke the FEC driver. It is possible that "something" was not
>the IDE support in fact, but yet something else.
>
>
On my side, I had the timeouts problems on tftp transferts from the
begining.
IDE support didn't change anything, the problem exists before.
>The MII initialization code used to work fine for us, as far as we
>were able to tell. Without having investigated this more closely, I
>will not check in this patch as I feel it might just fix some
>symptoms.
>
>
For me, this init is useless, the MII takes its configuration from hardware.
On MPC8xx boards, there's no such init sequence and FEC works fine
for all boards.
>
>Best regards,
>
>Wolfgang Denk
>
>
>
Best regards
next prev parent reply other threads:[~2004-03-25 9:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 8:27 [U-Boot-Users] PATCH: fix FEC problems on MPC5200 Pierre AUBERT
2004-03-25 9:02 ` Wolfgang Denk
2004-03-25 9:17 ` Pierre AUBERT [this message]
2004-03-25 9:40 ` Wolfgang Denk
2004-03-25 9:57 ` Pierre AUBERT
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=4062A3C1.40107@staubli.com \
--to=p.aubert@staubli.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.