summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAras Vaichas <arasv@magtech.com.au>2008-03-26 09:43:57 +1100
committerBen Warren <biggerbadderben@gmail.com>2008-03-30 00:09:49 -0400
commitd9a2f416d6ac6058cd7845033ae4dc32ef1c0746 (patch)
tree201a2451d25d1af825df667a3f32e03aa9f2834d /README
parent74d1e66d22dac91388bc538b2fe19f735edc5b82 (diff)
DHCP request fix for Windows Server 2003
Added option CONFIG_BOOTP_DHCP_REQUEST_DELAY. This provides an optional delay before sending "DHCP Request" in net/bootp.c. Required to overcome interoperability problems with Windows Server 200x DHCP server when U-Boot client responds too fast for server to handle. Signed-off-by: Aras Vaichas <arasv@magtech.com.au> Signed-off-by: Ben Warren <biggerbadderben@gmail.com>
Diffstat (limited to 'README')
-rw-r--r--README14
1 files changed, 14 insertions, 0 deletions
diff --git a/README b/README
index 5cbe7c1e8..592d1d884 100644
--- a/README
+++ b/README
@@ -1151,6 +1151,20 @@ The following options need to be configured:
of the "hostname" environment variable is passed as
option 12 to the DHCP server.
+ 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.
+
- CDP Options:
CONFIG_CDP_DEVICE_ID