From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shinya Kuribayashi Date: Tue, 08 Jul 2008 22:55:56 +0900 Subject: [U-Boot-Users] [PATCH] mips: When booting Linux images, add'ethaddr' and 'eth1addr' to the environment In-Reply-To: <1215438409.31842.61.camel@mcmullan-linux.cifs.lab.netapp.com> References: <20080609035837.84DD36EACD@mcmullan-linux.hq.netapp.com> <48705F2C.4020406@ruby.dti.ne.jp> <1215438409.31842.61.camel@mcmullan-linux.cifs.lab.netapp.com> Message-ID: <487371EC.4040003@ruby.dti.ne.jp> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de McMullan, Jason wrote: > On Sun, 2008-07-06 at 14:59 +0900, Shinya Kuribayashi wrote: >> Jason McMullan wrote: >>> Add 'ethaddr' and 'eth1addr' to the Linux kernel environment if >>> they are set in the U-Boot environment. >> Looking closely into linux/arch/*, I found that mips is the only >> architecture which supports the 'ethaddr' kernel parameter. Is this >> right? What I want to make sure is whether 'ethaddr' is an unusual >> kernel parameter or not. > > On our devices, the U-Boot environment is the only place the ethernet > MAC address is stored. > > Since the infrastructure for passing environment variables up to the > MIPS Linux kernel existed anyways, I decided that it would be a better > plan to use that machanism than to have the kernel dig through the > duplicate U-Boot environments. Thanks for the explanations. As Linux/MIPS kernel supports this parameter anyway, it's good for U-Boot to support that, too. Applied, will send to Wolfgang asap. Shinya