binman: Read the fit entries only once

[platform/kernel/u-boot.git] / README

diff --git a/README b/README
index 5d2c1ba..6bb8d6e 100644 (file)
--- a/README
+++ b/README
@@ -1172,35 +1172,6 @@ The following options need to be configured:
                from a BOOTP client in networks with unusually high latency.
 
 - DHCP Advanced Options:
-               You can fine tune the DHCP functionality by defining
-               CONFIG_BOOTP_* symbols:
-
-               CONFIG_BOOTP_NISDOMAIN
-               CONFIG_BOOTP_BOOTFILESIZE
-               CONFIG_BOOTP_NTPSERVER
-               CONFIG_BOOTP_TIMEOFFSET
-               CONFIG_BOOTP_VENDOREX
-               CONFIG_BOOTP_MAY_FAIL
-
-               CONFIG_BOOTP_MAY_FAIL - If the DHCP server is not found
-               after the configured retry count, the call will fail
-               instead of starting over.  This can be used to fail over
-               to Link-local IP address configuration if the DHCP server
-               is not available.
-
-               CONFIG_BOOTP_DHCP_REQUEST_DELAY
-
-               A 32bit value in microseconds for a delay between
-               receiving a "DHCP Offer" and sending the "DHCP Request".
-               This fixes a problem with certain DHCP servers that don't
-               respond 100% of the time to a "DHCP request". E.g. On an
-               AT91RM9200 processor running at 180MHz, this delay needed
-               to be *at least* 15,000 usec before a Windows Server 2003
-               DHCP server would reply 100% of the time. I recommend at
-               least 50,000 usec to be safe. The alternative is to hope
-               that one of the retries will be successful but note that
-               the DHCP timeout and retry process takes a longer than
-               this delay.
 
  - Link-local IP address negotiation:
                Negotiate with other link-local clients on the local network