mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: "Jan Lübbe" <jlu@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: Verified boot support with FIT
Date: Fri, 15 Jan 2016 18:18:06 -0700	[thread overview]
Message-ID: <CAPnjgZ1v8T_nbBg4xiBT+XcWxoK2gKCTm4PYxAKexi5xU-Y3wA@mail.gmail.com> (raw)
In-Reply-To: <1452846986.2915.110.camel@pengutronix.de>

Hi Jan,

On 15 January 2016 at 01:36, Jan Lübbe <jlu@pengutronix.de> wrote:
> 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?

The verified boot implementation looks like it came from U-Boot.

Regards,
Simon

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2016-01-16  1:18 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
2016-01-16  1:18     ` Simon Glass [this message]
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=CAPnjgZ1v8T_nbBg4xiBT+XcWxoK2gKCTm4PYxAKexi5xU-Y3wA@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=barebox@lists.infradead.org \
    --cc=jlu@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