"tftp: adjust settings to be suitable for 100Mbit ethernet" breaks imx6
Peng Fan
Acked-by Joe HershbergerHi,
With the following patch, I met tftp errors on mx6qsabresd and mx6ul boards:
"
=> setenv serverip 10.193.102.217; setenv ipaddr 10.193.102.31;tftp ${loadaddr} zImage Using FEC device
TFTP from server 10.193.102.217; our IP address is 10.193.102.31 Filename 'zImage'.
Load address: 0x12000000
Loading: *
TFTP error: 'Failure to negotiate RFC1782 options' (8)
Starting again
"
Without the following patch, tftp work fine on mx6qsabresd and mx6ul board.
"
commit 620776d734e4b126c407f636bda825a594a17723
Author: Pavel Machek <[email protected]> Date: Tue Aug 18 14:34:26 2015 +0200
tftp: adjust settings to be suitable for 100Mbit ethernet
Adjust timouts and retry counts to be suitable for loaded ethernet network. With 5 seconds timeout, 10 retries maximum, tftp is impossible even on local network with single full-speed TCP connection.
100msec timeout should be suitable for most networks tftp is used on, that is local ethernets. Timeout count really needs to be way higher, as lost packets are normal when TCP is running over the same network.
Enforce 10msec minimum.
"
Regards,
Peng.
Hi Peng,
Quoted 32 lines · Peng Fan
Hi,
With the following patch, I met tftp errors on mx6qsabresd and mx6ul boards:
"
=> setenv serverip 10.193.102.217; setenv ipaddr 10.193.102.31;tftp ${loadaddr} zImage Using FEC device
TFTP from server 10.193.102.217; our IP address is 10.193.102.31 Filename 'zImage'.
Load address:0x12000000
Loading: *
TFTP error: 'Failure to negotiate RFC1782 options' (8)
Starting again
"Without the following patch, tftp work fine on mx6qsabresd and mx6ul board.
"
commit620776d734e4b126c407f636bda825a594a17723Author: Pavel Machek <[email protected]> Date: Tue Aug 18 14:34:26 2015 +0200tftp: adjust settings to be suitable for 100Mbit ethernet
Adjust timouts and retry counts to be suitable for loaded ethernet network. With 5 seconds timeout, 10 retries maximum, tftp is impossible even on local network with single full-speed TCP connection.
100msec timeout should be suitable for most networks tftp is used on, that is local ethernets. Timeout count really needs to be way higher, as lost packets are normal when TCP is running over the same network.
Quoted 6 lines
Enforce 10msec minimum.
Signed-off-by Pavel Machek <[email protected]>Acked-by Joe Hershberger <[email protected]>"
The revert patch [1] has already been applied in the u-boot-x86/master branch, waiting for upstream.
[1] http://git.denx.de/?p=u-boot/u-boot-x86.git;a=commitdiff;h=527ba17bfd058bd87d5ed4c65aa6f31bebb25dfe
Regards,
Bin
Hi Bin,
Quoted 42 lines · Bin Meng
Hi Peng,
Quoted 32 lines · Peng Fan
Hi,
With the following patch, I met tftp errors on mx6qsabresd and mx6ul boards:
"
=> setenv serverip 10.193.102.217; setenv ipaddr 10.193.102.31;tftp ${loadaddr} zImage Using FEC device
TFTP from server 10.193.102.217; our IP address is 10.193.102.31 Filename 'zImage'.
Load address:0x12000000
Loading: *
TFTP error: 'Failure to negotiate RFC1782 options' (8)
Starting again
"Without the following patch, tftp work fine on mx6qsabresd and mx6ul board.
"
commit620776d734e4b126c407f636bda825a594a17723Author: Pavel Machek <[email protected]> Date: Tue Aug 18 14:34:26 2015 +0200tftp: adjust settings to be suitable for 100Mbit ethernet
Adjust timouts and retry counts to be suitable for loaded ethernet network. With 5 seconds timeout, 10 retries maximum, tftp is impossible even on local network with single full-speed TCP connection.
100msec timeout should be suitable for most networks tftp is used on, that is local ethernets. Timeout count really needs to be way higher, as lost packets are normal when TCP is running over the same network.
Quoted 6 lines
Enforce 10msec minimum.
Signed-off-by Pavel Machek <[email protected]>Acked-by Joe Hershberger <[email protected]>"
Quoted 4 lines
The revert patch [1] has already been applied in the u-boot-x86/master branch, waiting for upstream.
[1] http://git.denx.de/?p=u-boot/u-boot-x86.git;a=commitdiff;h=527ba17bfd058bd87d5ed4c65aa6f31bebb25dfe
Thanks for this.
Regards,
Peng.
Quoted 3 lines
Regards,
Bin