From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] powerpc/CoreNet: add tool to support pbl image build.
Date: Thu, 7 Jun 2012 11:52:02 -0500 [thread overview]
Message-ID: <4FD0DC32.7040505@freescale.com> (raw)
In-Reply-To: <ED492CCEAF882048BC2237DE806547C9079689E3@039-SN2MPN1-012.039d.mgd.msft.net>
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.
-Scott
next prev parent reply other threads:[~2012-06-07 16:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 8:57 [U-Boot] [PATCH] powerpc/CoreNet: add tool to support pbl image build Shaohui Xie
2012-06-05 0:32 ` Scott Wood
2012-06-05 5:35 ` Xie Shaohui-B21989
2012-06-05 18:14 ` Scott Wood
2012-06-06 2:45 ` Xie Shaohui-B21989
2012-06-06 18:18 ` Scott Wood
2012-06-07 3:16 ` Xie Shaohui-B21989
2012-06-07 16:52 ` Scott Wood [this message]
2012-06-08 2:55 ` Xie Shaohui-B21989
2012-06-08 16:09 ` Scott Wood
2012-06-12 17:42 ` Tabi Timur-B04825
2012-06-12 17:54 ` Scott Wood
2012-06-13 15:29 ` Tabi Timur-B04825
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=4FD0DC32.7040505@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