From mboxrd@z Thu Jan  1 00:00:00 1970
From: Joe Hamman <joe.hamman@embeddedspecialties.com>
Date: Mon, 17 Dec 2007 14:27:22 -0600
Subject: [U-Boot-Users] Device tree and u-boot passing MAC
	addressquestions
In-Reply-To: <f87675ee0712171047n1e7a290cibbfff3e2ad2167e4@mail.gmail.com>
References: <f87675ee0712170956u221bd595x321aac82f856136@mail.gmail.com><4766C201.1070904@freescale.com>
	<f87675ee0712171047n1e7a290cibbfff3e2ad2167e4@mail.gmail.com>
Message-ID: <005f01c840eb$3b0bcb20$7100a8c0@ESIDT>
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

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