All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: "Hernandez, Carlos" <ceh@ti.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: [PATCH] recipe: u-boot: update recipe for more images
Date: Tue, 26 Feb 2013 15:27:39 -0500	[thread overview]
Message-ID: <512D1ABB.4080304@ti.com> (raw)
In-Reply-To: <32B5D12402BE454796026F6AC58AA86E2E71F333@DLEE09.ent.ti.com>

On 02/26/2013 03:13 PM, Hernandez, Carlos wrote:
>> I haven't seen the keystone patches yet, so I don't know if the GPH
>> image is "special" in terms of headers, but the build target
>> u-boot-with-spl.bin is the canonical build target for "put
>> u-boot-spl.bin and u-boot.bin together".
>>
> 
> The current test script transfers (via UART) u-boot-spl.bin and then u-boot.img. 
> Have anybody tried booting one omap or sitara device using 'u-boot-with-spl.bin' image.

No, because none of the boot modes that take u-boot-spl.bin would like
to see a concatenated image like that.  That build target is primarily
used on other (vendors) platforms.

-- 
Tom


      reply	other threads:[~2013-02-26 20:27 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
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 [this message]

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=512D1ABB.4080304@ti.com \
    --to=trini@ti.com \
    --cc=ceh@ti.com \
    --cc=meta-ti@yoctoproject.org \
    /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.