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. I don't consider this patch a "must have" for upstream. I try to make sure all the changes that are needed for our product are sent to the u-boot list, even if they don't end up being accepted for DENX's U-Boot. On a completely unrelated topic, I really like the MIPS 'environment' method of passing information to the kernel instead of the old 'bd_t' method. It's a lot more flexible. Jason McMullan MTS SW System Firmware NetApp 724.741.5011 Fax 724.741.5166 Direct 412.656.3519 Mobile [EMAIL PROTECTED] www.netapp.com
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________ U-Boot-Users mailing list U-Boot-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/u-boot-users
