X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=doc%2FREADME.enetaddr;h=2d8e24f5cb4df128dcf5fdba00ed244614791f25;hb=797449a16d7f56ce1a7e38e3d85061f933b92c17;hp=94d800a02ae0ff437746030587fbc65a75d49276;hpb=83653121d7382fccfe329cb732f77f116341ef1d;p=u-boot

diff --git a/doc/README.enetaddr b/doc/README.enetaddr
index 94d800a02a..2d8e24f5cb 100644
--- a/doc/README.enetaddr
+++ b/doc/README.enetaddr
@@ -33,11 +33,13 @@ Correct flow of setting up the MAC address (summarized):
 1. Read from hardware in initialize() function
 2. Read from environment in net/eth.c after initialize()
 3. Give priority to the value in the environment if a conflict
-4. Program hardware in the device's init() function.
+4. Program the address into hardware if the following conditions are met:
+	a) The relevant driver has a 'write_addr' function
+	b) The user hasn't set an 'ethmacskip' environment variable
+	c) The address is valid (unicast, not all-zeros)
 
-If somebody wants to subvert the design philosophy, this can be done
-in the board-specific board_eth_init() function by calling eth_init()
-after all the NICs have been registered.
+Previous behavior had the MAC address always being programmed into hardware
+in the device's init() function.
 
 -------
  Usage