[U-Boot] [PATCH] powerpc/CoreNet: add tool to support pbl image build.

[Scott Wood]

On 06/07/2012 09:55 PM, Xie Shaohui-B21989 wrote:
>> On 06/06/2012 10:16 PM, Xie Shaohui-B21989 wrote:
>>>> -----Original Message-----
>>>> From: Wood Scott-B07421
>>>> Sent: Thursday, June 07, 2012 2:19 AM
>>>> To: Xie Shaohui-B21989
>>>> Cc: Wood Scott-B07421; u-boot at lists.denx.de; Tabi Timur-B04825
>>>> Subject: Re: [U-Boot] [PATCH] powerpc/CoreNet: add tool to support
>>>> pbl image build.
>>>>
>>>> On 06/05/2012 09:45 PM, Xie Shaohui-B21989 wrote:
>>>>> Can Timur's
>>>>> tool do it automatically, or by some arguments provided? And even
>>>>> though, there will be two files for configuration, one is RCW output
>>>>> from Timur's tool, and another is PBI commands. This is too much for
>>>>> the tool; it has only one entry for configuration file.
>>>>
>>>> Too much for which tool, and why can't that be changed?
>>>
>>> [Xie Shaohui]  The mkimage structure provides one entry to indicate
>>> the configuration file, is it OK to add a more entry just for PBL?
>>
>> I don't see why not.
> 
> [Xie Shaohui] OK. Then I'll split the current configuration file in two,
> one is for RCW, another is for PBI commands. Also, add one more entry for
> the second configuration file. But as you know, Timur's tool is not in
> open source now, I can only use a default RCW file for now.
> 
> I have two questions:
> 1. Is there a plan that we submit Timur' tool to open source?

I hope so.  If not, the RCW will have to be provided directly as a
hexdump/binary/etc.

> 2. If yes, should I combine Timur's tool with my tool or I just tell user
> They should use Timur's tool to produce the RCW and then use it in my tool?

They should be separate, since there are situations where you just want
the RCW and not the PBL image loading -- but it should all be an
automatic part of the U-Boot bulid process for targets that require it.

-Scott