From: Mike Scheutzow <scheutzow@alcatel-lucent.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Yucca ethernet timeout
Date: Sat, 10 Mar 2007 09:45:56 -0500 [thread overview]
Message-ID: <45F2C4A4.3060006@alcatel-lucent.com> (raw)
In-Reply-To: <200703092024.14459.sr@denx.de>
Stefan Roese wrote:
> On Friday 09 March 2007 15:01, Dale Dunlea wrote:
>> Since the upgrade, I'm seeing timeouts during TFTP.
> How often does it happen? Has your network lot's of broadcast messages?
I see this timeout problem on my mpc8343 port, using 1.1.4 network code.
Prior to my workaround, it happened on 99% of the tftp transfers. My
u-boot test network is tiny (3 machines, 100 Mbps), and has almost no
traffic on it. The bug appears when code optimization (-Os) is on, but
does not occur with no optimization.
My workaround was to add a delay of 100 usec at the bottom of the
receive polling loop (in net/net.c, I believe.) A delay of 10 usec did
not cure the symptom.
--
Mike Scheutzow
scheutzow at alcatel-lucent.com
next prev parent reply other threads:[~2007-03-10 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 14:01 [U-Boot-Users] Yucca ethernet timeout Dale Dunlea
2007-03-09 19:24 ` Stefan Roese
2007-03-10 14:45 ` Mike Scheutzow [this message]
2007-03-11 12:37 ` Stefan Roese
2007-03-12 12:20 ` Mike Scheutzow
2007-03-11 12:48 ` Dale Dunlea
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=45F2C4A4.3060006@alcatel-lucent.com \
--to=scheutzow@alcatel-lucent.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