From: Simon Kagstrom Date: Mon, 7 Sep 2009 09:44:56 +0200 Subject: [U-Boot] [PATCH 1/1] at91: Update MEESC board support In-Reply-To: <4AA4B599.7090609@esd.eu> References: <12520673913026-git-send-email-Daniel.Gorsulowski@esd.eu> <20090904211358.GR30118@game.jcrosoft.org> <20090904220234.EDC99832E8DE@gemini.denx.de> <4AA4B599.7090609@esd.eu> Message-ID: <20090907094456.6f35313b@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 Mon, 07 Sep 2009 09:26:17 +0200 Daniel Gorsulowski wrote: >> nack this will be done when u-boot will need to use the macb# > Just imagine: U-boot boots a Linux kernel from NAND flash. It does NOT need the > ethernet interface, so it does NOT initialize ethernet, so the ethernet address > will NOT be written to the EMAC module! > As a result, Linux will assign a random address, that is not acceptable! Unfortunately, you'll have to communicate this in some other way to Linux. I also had this problem and submitted a patch for it. In the replies there were some suggestions on how to handle this: http://lists.denx.de/pipermail/u-boot/2009-July/055725.html Unfortunately, there is no standard way of doing this on ARM. Some people want to introduce PowerPC-style device trees on ARM as well, where this is handled in a generic way, but that hasn't been done yet and requires changes on both the Linux-side and U-boot. So I believe this kind of patches will not be accepted, unfortunately. If you depend on the behavior, you can obviously keep the patch in your own tree. // Simon