From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1 1/1] fastboot: Add support for flashing zImage
Date: Mon, 2 Mar 2015 10:40:15 -0500 [thread overview]
Message-ID: <20150302154015.GU29891@bill-the-cat> (raw)
In-Reply-To: <CAL_Jsq+grtjpgNFJsOjZ67eZftcieOsQQ-Zhy_iJ_YtSqdoGZw@mail.gmail.com>
On Wed, Feb 25, 2015 at 06:30:30PM -0600, Rob Herring wrote:
> On Wed, Feb 25, 2015 at 4:56 PM, Dileep Katta <dileep.katta@linaro.org> wrote:
> > This patch adds support to flash zImage to the boot partition on eMMC.
> > Usage: fastboot flash zImage <path_to_zImage>
>
> So this replaces the kernel in an existing bootimage. What's wrong
> with "fastboot flash boot", "fastboot flash:raw boot <kernel>" or
> "fastboot boot <kernel>"? It is a bit fragile to be updating your
> kernel without updating the ramdisk. arm64 has no zImage, so this
> command is somewhat arm32 specific.
>
> Fastboot is already plagued with a variety of implementations and
> behaviors. Some unification here would be good and just adding
> whatever various commands have been added to vendor u-boot's is not
> going to help. Adding to the combinations of things to test also
> bothers me.
+1. Just how much room do we have, or not have, to be compatible with
existing tools but also abstract some of this out so that different
boards can "I want a layout like this ..." (one set of kernel, device
tree, initrd) and another "I want a layout like this ..." (two sets, for
redundancy).
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150302/9a845458/attachment.sig>
next prev parent reply other threads:[~2015-03-02 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 22:56 [U-Boot] [PATCH v1 1/1] fastboot: Add support for flashing zImage Dileep Katta
2015-02-26 0:30 ` Rob Herring
2015-03-02 15:40 ` Tom Rini [this message]
2015-03-04 13:08 ` Lukasz Majewski
2015-03-05 14:29 ` Dileep Katta
2015-03-12 9:20 ` Lukasz Majewski
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=20150302154015.GU29891@bill-the-cat \
--to=trini@konsulko.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