From mboxrd@z Thu Jan  1 00:00:00 1970
From: Scott Wood <scottwood@freescale.com>
Date: Fri, 25 May 2007 13:17:10 -0500
Subject: [U-Boot-Users] Imminent u-boot-fdt pull request
In-Reply-To: <465727AA.3040104@smiths-aerospace.com>
References: <46526C2E.3070100@gmail.com>	<20070524222612.381a3587.kim.phillips@freescale.com>	<4656AC13.2010300@grandegger.com>	<20070525105833.3d1dbd0e.kim.phillips@freescale.com>
	<4657152D.7030606@smiths-aerospace.com>
	<4657255C.8040405@freescale.com>
	<465727AA.3040104@smiths-aerospace.com>
Message-ID: <46572826.4090307@freescale.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

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