From: "Jan Lübbe" <jlu@pengutronix.de>
To: Marc Kleine-Budde <mkl@pengutronix.de>, Simon Glass <sjg@chromium.org>
Cc: barebox@lists.infradead.org
Subject: Re: Verified boot support with FIT
Date: Fri, 15 Jan 2016 09:36:26 +0100 [thread overview]
Message-ID: <1452846986.2915.110.camel@pengutronix.de> (raw)
In-Reply-To: <5697FF03.1060702@pengutronix.de>
On Do, 2016-01-14 at 21:03 +0100, Marc Kleine-Budde wrote:
> On 01/14/2016 08:30 PM, Simon Glass wrote:
> > Someone pointed me to this support that is being added in Barebox. I see
> > that it still has the copyright but does not attribute U-Boot. I'm just
> > checking if that is that an oversight?
>
> I've Cc'ed Jan, who has written the code. Quoting from his first patch
> to the barebox mailinglist:
>
> > this is the current work-in-progress state of my FIT support patches.
> > The FIT loading code has basically been rewritten from scratch, as the
> > original U-Boot code uses libfdt and barebox's DT support works on an
> > in-memory tree.
Yes, this is still correct for the recent submissions.
The barebox code only supports the signed configurations with hashed
images, as the goal was to use this for verified boot. Supporting only
this mode keeps the complexity down.
Simon, do you think it is a derived work of the U-Boot FIT code?
Regards,
Jan Lübbe
--
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:[~2016-01-15 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPnjgZ187+14Fn-aeBkzV9Yv7MXOYPbTJjzCrHByuO04=OoAww@mail.gmail.com>
2016-01-14 20:03 ` Marc Kleine-Budde
2016-01-15 8:36 ` Jan Lübbe [this message]
2016-01-16 1:18 ` Simon Glass
2016-01-14 20:05 Simon Glass
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=1452846986.2915.110.camel@pengutronix.de \
--to=jlu@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=mkl@pengutronix.de \
--cc=sjg@chromium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox