From: Carlos Hernandez <ceh@ti.com>
To: Tom Rini <trini@ti.com>
Cc: meta-ti@yoctoproject.org
Subject: Re: [PATCH] recipe: u-boot: update recipe for more images
Date: Tue, 26 Feb 2013 15:38:03 -0500 [thread overview]
Message-ID: <512D1D2B.7080909@ti.com> (raw)
In-Reply-To: <512D1A7F.7030806@ti.com>
On 02/26/2013 03:26 PM, Tom Rini wrote:
> On 02/26/2013 03:12 PM, Cyril Chemparathy wrote:
>> On 02/26/2013 02:53 PM, Murali Karicheri wrote:
>>> + Cyril,
>>>
>>> Cyril had worked on adding GPH format for u-boot. Want to hear from him
>>> why not used the u-boot-with-spl.bin build target.
>>>
>> Because u-boot-with-spl.bin does not wrap the spl image with a header
>> that the rom bootloader understands.
> What is the header we need? I assume it's not compatible with our
> previous headers. And if it's just a convenience for programming the
> flash, maybe we just stick with two files, to avoid further headaches
> upstream? It's a general rule that concatenating files would make
> programming easier, but it's a small savings on either end, yes? This
> would also make the packaging easier since it would just be
> SPL_IMAGE_FILE (or whatever) set to u-boot-spl.gph and so forth. Thanks!
>
I believe this is what the patch I submitted (to meta-arago) few days
ago do.
You need to define SPL_UART_BINARY in your recipe to enable the extra
do_install and do_deploy functionality.
next prev parent reply other threads:[~2013-02-26 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 18:38 [PATCH] recipe: u-boot: update recipe for more images Murali Karicheri
2013-02-26 18:42 ` Murali Karicheri
2013-02-26 19:20 ` Denys Dmytriyenko
2013-02-26 19:31 ` Tom Rini
2013-02-26 19:53 ` Murali Karicheri
2013-02-26 20:02 ` Denys Dmytriyenko
2013-02-26 20:07 ` Denys Dmytriyenko
2013-02-26 20:12 ` Cyril Chemparathy
2013-02-26 20:26 ` Tom Rini
2013-02-26 20:38 ` Carlos Hernandez [this message]
2013-02-26 21:22 ` Denys Dmytriyenko
2013-02-26 21:25 ` Tom Rini
2013-02-26 20:13 ` Hernandez, Carlos
2013-02-26 20:27 ` Tom Rini
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=512D1D2B.7080909@ti.com \
--to=ceh@ti.com \
--cc=meta-ti@yoctoproject.org \
--cc=trini@ti.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.