public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Imminent u-boot-fdt pull request
Date: Fri, 25 May 2007 14:31:11 -0400	[thread overview]
Message-ID: <46572B6F.3050409@smiths-aerospace.com> (raw)
In-Reply-To: <46572826.4090307@freescale.com>

Scott Wood wrote:
> Jerry Van Baren wrote:
>>> 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
>>
>>
>> I deeply regret the confusion I caused by pushing the "Send" when I 
>> meant to push "Write" to start a new, unrelated, message.  My updated 
>> re-send, as you probably have figured out by now, is more coherent.
>>
>> OF_CPU is defined in the board-specific header file, e.g. 
>> configs/MPC8360EMDS.h, pulled in by config.h.  Since I am missing the 
>> #include <config.h> in the two files being discussed, OF_CPU is 
>> undefined and the string concatenation trick makes it silently disappear.
> 
> Sure... I was just suggesting a more robust method, that doesn't rely on 
> the board config file to define the CPU name.
> 
> -Scott

Ah, now I follow.  That is worth considering.  That would make some 
assumptions too, just different ones.

Of the top of my head...
* All CPUs are clocked the same (unlikely to be a problem)
* That the CPU actually _needs_ the fixups (currently they all get the 
fixup so it isn't currently a problem)

As long as it works for the bootwrapper, it would work for u-boot.  The 
two are imperfect subsets of each other, however.

Thanks,
gvb

  reply	other threads:[~2007-05-25 18:31 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
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 [this message]
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=46572B6F.3050409@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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