From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Hamman Date: Mon, 17 Dec 2007 14:37:16 -0600 Subject: [U-Boot-Users] Device tree and u-boot passing MAC addressquestions In-Reply-To: <4766DC57.6080708@ge.com> References: <4766C201.1070904@freescale.com> <005f01c840eb$3b0bcb20$7100a8c0@ESIDT> <4766DC57.6080708@ge.com> Message-ID: <006001c840ec$9cf09090$7100a8c0@ESIDT> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > -----Original Message----- > From: Jerry Van Baren [mailto:gerald.vanbaren at ge.com] > Sent: Monday, December 17, 2007 2:30 PM > To: joe.hamman at embeddedspecialties.com > Cc: 'robert lazarski'; 'U-Boot-Users' > Subject: Re: [U-Boot-Users] Device tree and u-boot passing MAC > addressquestions > > Joe Hamman wrote: > > Hi Robert, > > > > [snip] > > > >> To get eth2 to link, I put this MAC in my device tree: > >> > >> local-mac-address = [ 00 E0 0C 00 02 FD ]; > >> > >> Otherwise the kernel just sees a series of zero's . Is this change on > >> purpose and I missed what I need to do now? > >> > > > > I recently encountered the same problem. By using the 'fdt b' command, > I > ^ > "fdt p" I presume. | Sorry, I should have listed all the steps: tftp 10000 filename.dtb # load the dtb fdt a 10000 # tell fdt where it loaded fdt b # do the board specific setup (fills in MAC) fdt p # verify the values are correct > > > was able to see that the MAC addresses were not being filled in prior to > > calling the kernel. > > > > Adding aliases to the dtb file fixed my problem. (Search the mailing > > lists...) > > > > Best regards, > > Joe