From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Imminent u-boot-fdt pull request
Date: Fri, 25 May 2007 13:05:16 -0500 [thread overview]
Message-ID: <4657255C.8040405@freescale.com> (raw)
In-Reply-To: <4657152D.7030606@smiths-aerospace.com>
Jerry Van Baren wrote:
> FWIIW, that is in the (infamous) common/fdt_support.c. It was adapted
> from ft_build.c. It looks like I lost a OF_CPU in the constructed
> string when I was adapting.
>
> Original code:
> p = ft_get_prop(blob, "/cpus/" OF_CPU "/clock-frequency", &len);
>
> Comments:
> 1) It looks like you are missing the OF_CPU definition, or I'm not
> pulling in the right .h file
What about doing a search for device_type = "cpu", rather than looking
for a specific CPU name? The Linux bootwrapper does it this way. It
also has the benefit of working when there's more than one CPU.
-Scott
next prev parent reply other threads:[~2007-05-25 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 4:06 [U-Boot-Users] Imminent u-boot-fdt pull request Jerry Van Baren
2007-05-25 3:26 ` Kim Phillips
2007-05-25 9:27 ` Wolfgang Grandegger
2007-05-25 15:58 ` Kim Phillips
2007-05-25 16:56 ` Jerry Van Baren
2007-05-25 17:13 ` Kim Phillips
2007-05-25 17:33 ` Jerry Van Baren
2007-05-25 19:36 ` Kim Phillips
2007-05-25 20:18 ` Jerry Van Baren
2007-05-25 18:05 ` Scott Wood [this message]
2007-05-25 18:12 ` [U-Boot-Users] HUSH local variables visibility in u-boot code Leonid
2007-05-25 19:33 ` Wolfgang Denk
2007-05-25 18:15 ` [U-Boot-Users] Imminent u-boot-fdt pull request Jerry Van Baren
2007-05-25 18:17 ` Scott Wood
2007-05-25 18:31 ` Jerry Van Baren
2007-05-25 17:06 ` Jerry Van Baren
2007-05-25 11:54 ` Jerry Van Baren
2007-05-25 15:58 ` Kim Phillips
2007-05-25 16:28 ` Jerry Van Baren
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=4657255C.8040405@freescale.com \
--to=scottwood@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