From: Pavel Machek <pavel@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] TFTP Timeout Interval problem
Date: Mon, 31 Aug 2015 14:16:13 +0200 [thread overview]
Message-ID: <20150831121613.GA7496@amd> (raw)
In-Reply-To: <BLUPR03MB504F1F574B141891FA26FDBED6B0@BLUPR03MB504.namprd03.prod.outlook.com>
Hi!
> I got a problem with tftp and found this patch.
Yes, sorry about that. Just revert it, or update to newer u-boot where
it should be reverted.
> -------------
> commit 620776d734e4b126c407f636bda825a594a17723
> Author: Pavel Machek <pavel@denx.de>
> Date: Tue Aug 18 14:34:26 2015 +0200
>
> tftp: adjust settings to be suitable for 100Mbit ethernet
> --------------
> The default timeout is changed to 100 (ms) and this causes "TFTP error: 'Unsupported option(s) requested' (8)".
>
> Because the option is equal to timeout/1000, now it's zero(100/1000 -> 0) which is not supported.
> Actually I find in an original doc RFC-2349 which specifies this value should range between "1" and "255" seconds.
>
> So I think there may be a conflict?
> Look forward to your help.
>
> This is my test log:
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: *
> TFTP error: 'Unsupported option(s) requested' (8)
> Starting again
> => setenv tftptimeout 1000
> => tftp a0000000 gqy/bootscript
> Using FM1 at DTSEC3 device
> TFTP from server 10.192.208.233; our IP address is 10.193.20.130
> Filename 'gqy/bootscript'.
> Load address: 0xa0000000
> Loading: #
> 44.9 KiB/s
> done
> Bytes transferred = 92 (5c hex)
> =>
>
> Regards,
> Qianyu
>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2015-08-31 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 10:43 [U-Boot] TFTP Timeout Interval problem Gong Q.Y.
2015-08-31 12:16 ` Pavel Machek [this message]
2015-09-01 2:49 ` Gong Q.Y.
2015-08-31 13:20 ` Bin Meng
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=20150831121613.GA7496@amd \
--to=pavel@denx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.