From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Device tree and u-boot passing MAC addressquestions
Date: Mon, 17 Dec 2007 14:56:10 -0600 [thread overview]
Message-ID: <4766E26A.4080300@freescale.com> (raw)
In-Reply-To: <005f01c840eb$3b0bcb20$7100a8c0@ESIDT>
Joe Hamman wrote:
> 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.
Most device tree properties are not filled in until you execute the bootm
command. The MAC address is one such property.
> Adding aliases to the dtb file fixed my problem. (Search the mailing
> lists...)
It looks like U-Boot was updated before the device trees were updated. When the
code for aliases was added to U-Boot, the code for older device trees should not
have been removed.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2007-12-17 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 17:56 [U-Boot-Users] Device tree and u-boot passing MAC address questions robert lazarski
2007-12-17 18:37 ` Timur Tabi
2007-12-17 18:47 ` robert lazarski
2007-12-17 20:27 ` [U-Boot-Users] Device tree and u-boot passing MAC addressquestions Joe Hamman
2007-12-17 20:30 ` Jerry Van Baren
2007-12-17 20:37 ` Joe Hamman
2007-12-17 20:56 ` Timur Tabi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4766E26A.4080300@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox