From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH 1/2] scripts: imx-image: Do not pad image
Date: Wed, 15 Jul 2015 14:06:20 +0200 [thread overview]
Message-ID: <20150715120620.GW18700@pengutronix.de> (raw)
In-Reply-To: <55A63FB1.2020804@pengutronix.de>
On Wed, Jul 15, 2015 at 01:10:41PM +0200, Marc Kleine-Budde wrote:
> On 07/15/2015 08:02 AM, Sascha Hauer wrote:
> > We have to pad the load size to the next 4k boundary, but we don't
> > need to pad the image itself since we do not care what data the ROM
> > actually loads.
> >
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>
> NACK - We do for the HABv4 case.
Hm, I just wanted to make that optional, the first option letter that
came to my mind was -p for padding. Shortly afterwards I noticed this already exists
and is for: "-p prepare image for signing". Can we attach the
padding to this option?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-07-15 12:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 6:02 Sascha Hauer
2015-07-15 6:02 ` [PATCH 2/2] scripts: imx-image: Make in-place capable Sascha Hauer
2015-07-15 11:10 ` [PATCH 1/2] scripts: imx-image: Do not pad image Marc Kleine-Budde
2015-07-15 12:06 ` Sascha Hauer [this message]
2015-07-15 12:09 ` Marc Kleine-Budde
2015-07-16 7:48 [PATCH v2]: imx-image changes Sascha Hauer
2015-07-16 7:48 ` [PATCH 1/2] scripts: imx-image: Do not pad image Sascha Hauer
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=20150715120620.GW18700@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mkl@pengutronix.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