From: NZG <ngustavson@emacinc.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: More 5282 network issues-development
Date: Tue, 12 Apr 2005 10:51:07 -0500 [thread overview]
Message-ID: <200504121051.07764.ngustavson@emacinc.com> (raw)
In-Reply-To: <200504121014.42518.ngustavson@emacinc.com>
> SPEED:
> The new code can download intact linux images with tftp, but it only works
> if ET_DEBUG is enabled. If it's not everything seems to run too fast and
> the code chokes itself(sends out big bursts of packets and then doesn't
> respond to the big bursts it gets back). How can I tell it to slow down and
> wait for responses without debug statements? Is there a place for this?
I think I see the problem, the network is expecting to be able to do ulong
delays, while the timer is only 16 bits. I'm going to monkey with the timer
code and see if I can get something set up.
NZG.
next prev parent reply other threads:[~2005-04-12 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 15:14 [U-Boot-Users] More 5282 network issues-development NZG
2005-04-12 15:51 ` NZG [this message]
2005-04-12 20:05 ` [U-Boot-Users] " Wolfgang Denk
2005-04-12 17:51 ` Zachary Landau
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=200504121051.07764.ngustavson@emacinc.com \
--to=ngustavson@emacinc.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