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 09:27:48 +0100 [thread overview]
Message-ID: <40629804.5060107@staubli.com> (raw)
Hi everybody,
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 ?
CHANGELOG:
* Patch by Pierre Aubert 25 Mar 2004
Fix FEC problems on MPC5xxx: suppress timeouts on tftp.
Best regards
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: u-boot-fec-mpc5xxx.diff
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040325/a25acb7a/attachment.txt
next reply other threads:[~2004-03-25 8:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 8:27 Pierre AUBERT [this message]
2004-03-25 9:02 ` [U-Boot-Users] PATCH: fix FEC problems on MPC5200 Wolfgang Denk
2004-03-25 9:17 ` Pierre AUBERT
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=40629804.5060107@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox