From: Rafal Jaworowski <raj@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] TFTP block size is too high
Date: Thu, 24 Apr 2008 13:52:23 +0200 [thread overview]
Message-ID: <48107477.6090107@semihalf.com> (raw)
In-Reply-To: <480FDD24.9090909@genesysdesign.com.au>
Jared Holzman wrote:
> Does anyone else have problems with the new default tftp block size of 1468 (set
> in tftp.c) being too large? I was getting corruption of the d/led images until I
> dropped it down to 1200. I'm afraid I don't have time to determine the real
> maximum size before corruption occurs. Does someone else want to look into this?
What exactly is your set-up i.e. what version of U-Boot, architecture,
platform etc. are you running? I recall problems with MPC5121e that sound
familiar, which were caused by a bug/misconfiguration in the FEC driver, but
in this case we fixed the issue a couple of months ago. Maybe that's something
of that sort..
kind regards,
Rafal
next prev parent reply other threads:[~2008-04-24 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 1:06 [U-Boot-Users] TFTP block size is too high Jared Holzman
2008-04-24 11:52 ` Rafal Jaworowski [this message]
2008-04-24 14:54 ` Ben Warren
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=48107477.6090107@semihalf.com \
--to=raj@semihalf.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