From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jerry Van Baren <gerald.vanbaren@ge.com>
Date: Mon, 17 Dec 2007 15:30:15 -0500
Subject: [U-Boot-Users] Device tree and u-boot passing
	MAC	addressquestions
In-Reply-To: <005f01c840eb$3b0bcb20$7100a8c0@ESIDT>
References: <f87675ee0712170956u221bd595x321aac82f856136@mail.gmail.com><4766C201.1070904@freescale.com>	<f87675ee0712171047n1e7a290cibbfff3e2ad2167e4@mail.gmail.com>
	<005f01c840eb$3b0bcb20$7100a8c0@ESIDT>
Message-ID: <4766DC57.6080708@ge.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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.                                            |

> 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