From: Pierre AUBERT <p.aubert@staubli.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] FEC problems on MPC5200
Date: Fri, 19 Mar 2004 12:31:38 +0100 [thread overview]
Message-ID: <405ADA1A.1090008@staubli.com> (raw)
In-Reply-To: <OFD5ACD66A.AD267385-ON00256E5C.0036D054-00256E5C.00379419@marel.is>
J?n Benediktsson wrote:
>I see the same happen with my Lite5200. I get frequent timeouts when
>loading the kernel with TFTP.
>It also happens when using the Motorola dbug boot monitor to load via TFTP.
>Something seems to be wrong.
>
>
I also have the problem with dbug monitor. Is there any timeouts within
Linux kernel ?
>This happens very rarely when I am using our custom mpc823 board to load
>from the same TFTP server,
>
>
With other boards (based on MPC860T) we don't have any timeouts.
>but with Lite5200 it happens almost every time.
>
>Regards,
>Jon Benediktsson
>Marel hf.
>
>
Regards
next prev parent reply other threads:[~2004-03-19 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 10:03 [U-Boot-Users] FEC problems on MPC5200 Pierre AUBERT
2004-03-19 10:07 ` Jón Benediktsson
2004-03-19 11:31 ` Pierre AUBERT [this message]
2004-03-19 15:27 ` Jón Benediktsson
2004-03-19 10:46 ` Wolfgang Denk
2004-03-24 14:37 ` Pierre AUBERT
2004-03-19 11:06 ` R: " Figini Enzo
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=405ADA1A.1090008@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