From: Marc Kleine-Budde <mkl@pengutronix.de>
To: Yegor Yefremov <yegorslists@googlemail.com>
Cc: barebox <barebox@lists.infradead.org>, kernel@pengutronix.de
Subject: Re: [PATCH 3/3] bootm: add initial FIT support
Date: Tue, 5 Jan 2016 11:32:45 +0100 [thread overview]
Message-ID: <568B9BCD.9070509@pengutronix.de> (raw)
In-Reply-To: <CAGm1_kunZqatbVbE3AgS-wQdx-gUqeShE2PrHYwxgLX74DRRLw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1183 bytes --]
On 01/05/2016 11:28 AM, Yegor Yefremov wrote:
> Hi Marc,
>
> thanks for reposting the patches.
>
> On Tue, Jan 5, 2016 at 9:11 AM, Marc Kleine-Budde <mkl@pengutronix.de> wrote:
>> From: Jan Luebbe <jlu@pengutronix.de>
>>
>> This implementation is inspired by U-Boot's FIT support. Instead of
>> using libfdt (which does not exist in barebox), configuration signatures
>> are verified by using a simplified DT parser based on barebox's own
>> code.
>>
>> Currently, only signed configurations with hashed images are supported,
>> as the other variants are less useful for verified boot. Compatible FIT
>> images can be created using U-Boot's mkimage tool.
>
> What about unsigned images?
That's not our use case. We use plain zImages instead.
> I also get: unsupported algo crc32
> Is it intended to be supported?
Not for our usecase - feel free to add crc32 support.
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-01-05 10:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 8:11 [PATCH 0/3] FIT Support Marc Kleine-Budde
2016-01-05 8:11 ` [PATCH 1/3] crypto: add enum Marc Kleine-Budde
2016-01-05 16:54 ` Sam Ravnborg
2016-01-06 14:39 ` Marc Kleine-Budde
2016-01-06 16:55 ` Sam Ravnborg
2016-01-05 8:11 ` [PATCH 2/3] crypto: add RSA support Marc Kleine-Budde
2016-01-05 8:11 ` [PATCH 3/3] bootm: add initial FIT support Marc Kleine-Budde
2016-01-05 10:28 ` Yegor Yefremov
2016-01-05 10:32 ` Marc Kleine-Budde [this message]
2016-01-05 10:40 ` Yegor Yefremov
2016-01-05 11:54 ` Marc Kleine-Budde
2016-01-05 13:05 ` Yegor Yefremov
2016-01-05 13:50 ` Marc Kleine-Budde
2016-01-05 13:58 ` Yegor Yefremov
2016-01-07 17:09 ` Jan Lübbe
2016-01-08 10:36 ` Yegor Yefremov
2016-01-05 20:28 ` Trent Piepho
2016-01-06 16:09 ` Marc Kleine-Budde
2016-01-07 17:00 ` Jan Lübbe
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=568B9BCD.9070509@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=kernel@pengutronix.de \
--cc=yegorslists@googlemail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox