From: Simon Kagstrom Date: Mon, 13 Jul 2009 10:13:07 +0200 Subject: [U-Boot] [PATCH 1/4]: arm: Kirkwood: Set MAC address during registration for kirkwood egiga In-Reply-To: <20090711092757.53FDE832E416@gemini.denx.de> References: <20090708130134.4b100399@marrow.netinsight.se> <20090708130222.7b3381ae@marrow.netinsight.se> <4A56D52A.8010401@gmail.com> <20090710092452.492dfafe@marrow.netinsight.se> <20090711092757.53FDE832E416@gemini.denx.de> Message-ID: <20090713101307.30d3d13c@marrow.netinsight.se> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Sat, 11 Jul 2009 11:27:57 +0200 Wolfgang Denk wrote: > > Should Linux otherwise read the passed U-boot environment and set it up > > by itself? > > Unfortunately ARM Linux does not provide yet a standard way to pass > the MAC address from the boot loader. In the long term this problem > will be solved by using the device tree for ARM; in the meantime, > some drivers use a "ethaddr=" command line parameter (but that will > probably bring up discussions on the Linux front again). OK, so until ARM has moved to the device tree approach (and from LKML I see there is some vocal opposition to this), we'd still need to resort to some driver-specific hack [with Linux support] for this? Or is it OK to do some board-specific "hack" to initialize it like board/atmel/at91rm9200ek/misc.c does it? Coming from a PowerPC-setting, I must say I miss the device trees though :-) // Simon