-----Original Message----- From: U-Boot [mailto:u-boot-bounces@lists.denx.de] On Behalf Of amessier.tyco@gmail.com Sent: 1-Feb-16 5:09 PM
From: Alexandre Messier amessier@tycoint.com
There is currently one config option (CONFIG_NET_RETRY_COUNT) that is available to tune the retries of the network stack. Unfortunately, it is global to all protocols, and the value is interpreted differently in all of them.
Add a new environment variable that directly sets the retry period for BOOTP timeouts. If this new value is not set, the period is still derived from the default number of retries, or from CONFIG_NET_RETRY_COUNT if defined. When both the new variable is set and CONFIG_NET_RETRY_COUNT is defined, the variable has precedence.
Signed-off-by: Alexandre Messier amessier@tycoint.com
Changes since v1:
- Now uses an environment variable instead of a config option. This is to have a similar approach as TFTP towards how timeouts are controlled. (e.g. https://patchwork.ozlabs.org/patch/528815/)
- Title was changed, it was previously "net: bootp: Add BOOTP specific config for timeout value."
- Removed from patch series. v1 was in a series, but now the patch stands alone.
v1 can be found here: Patchwork: https://patchwork.ozlabs.org/patch/571776/ Mailing list: http://lists.denx.de/pipermail/u-boot/2016-January/242840.html
Hi Joe,
Is there any change this patch can make it into v2016.03?
Sylvain Lemieux
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
________________________________
This e-mail contains privileged and confidential information intended for the use of the addressees named above. If you are not the intended recipient of this e-mail, you are hereby notified that you must not disseminate, copy or take any action in respect of any information contained in it. If you have received this e-mail in error, please notify the sender immediately by e-mail and immediately destroy this e-mail and its attachments.