summaryrefslogtreecommitdiff
path: root/doc/README.enetaddr
diff options
context:
space:
mode:
authorHeiko Schocher <hs@denx.de>2010-03-31 08:34:51 +0200
committerWolfgang Denk <wd@denx.de>2010-03-31 15:13:32 +0200
commit8e64d6efd8d778a5f83d8bff9cd273a86dcc182f (patch)
tree53a7889f6bb780dbe10d284269dca09aa95821bf /doc/README.enetaddr
parentb78b48c6a0c34b2991e31fc4548aaf773d34f2b3 (diff)
net, doc: How to setup MAC address correctly
As this seems unclear, document how the flow of setting up the MAC address is correct. Signed-off-by: Heiko Schocher <hs@denx.de> Text changed slightly, adding input from Mike Frysinger. Signed-off-by: Wolfgang Denk <wd@denx.de>
Diffstat (limited to 'doc/README.enetaddr')
-rw-r--r--doc/README.enetaddr11
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/README.enetaddr b/doc/README.enetaddr
index 1d75aa3876e..94d800a02ae 100644
--- a/doc/README.enetaddr
+++ b/doc/README.enetaddr
@@ -28,6 +28,17 @@ Here are the places where MAC addresses might be stored:
purpose of passing this information to an OS kernel we are about
to boot
+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.
+
+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.
+
-------
Usage
-------