Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Christopher Larson <chris_larson@mentor.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] wic: Generate startup.nsh for EFI cases if none found
Date: Thu, 28 Sep 2017 14:04:42 -0400	[thread overview]
Message-ID: <20170928180442.GR3112@bill-the-cat> (raw)
In-Reply-To: <CAP9ODKoWKvzf9eKAbjPCe4MY5d8f2EsBSjXbA87Ouw46QHP+=w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

On Thu, Sep 28, 2017 at 03:01:13PM -0300, Otavio Salvador wrote:
> On Thu, Sep 28, 2017 at 2:59 PM, Tom Rini <trini@konsulko.com> wrote:
> > On Thu, Sep 28, 2017 at 02:57:04PM -0300, Otavio Salvador wrote:
> >> On Thu, Sep 28, 2017 at 2:49 PM, Tom Rini <trini@konsulko.com> wrote:
> >> > On Thu, Sep 28, 2017 at 02:46:23PM -0300, Otavio Salvador wrote:
> >> >> Hello Tom,
> >> >>
> >> >> On Thu, Sep 28, 2017 at 2:44 PM, Tom Rini <trini@konsulko.com> wrote:
> >> >> > On Thu, Sep 28, 2017 at 06:47:07PM +0300, Ed Bartosh wrote:
> >> >> >> On Wed, Sep 20, 2017 at 12:03:27PM -0400, Tom Rini wrote:
> >> >> >> > In the case of non-wic images there is logic today to generate a
> >> >> >> > startup.nsh file that will be executed by EFI to run the loader that the
> >> >> >> > image contains.  In the WIC case is currently depends on that file being
> >> >> >> > generated elsewhere and placed in DEPLOY_DIR_IMAGE and only used if
> >> >> >> > present there.
> >> >> >>
> >> >> >> What's wrong with this approach?
> >> >> >
> >> >> > No one ever provides a startup.nsh and everyone that wants one creates
> >> >> > the same one line trivial example.  The end result is that no WIC images
> >> >> > are Just Bootable on UEFI systems unless you first go and spell that out
> >> >> > as the desired booting device.  This isn't an awesome workflow which is
> >> >> > why the non-WIC cases make the required startup.nsh :)
> >> >>
> >> >> I think it could be done as we did for u-boot-extlinux support.
> >> >
> >> > That's complete overkill for a static one line file.
> >>
> >> No, it is not. It allows for reproducable builds.
> >
> > Either solution would allow for reproducible builds.  Perhaps it would
> > be clearer if the patch just always generated that content instead like
> > the systemd and grub2 classes do?
> 
> No; if the file is generated by wic it is external of the build and
> thus can change without the image change.

WIC isn't external to the build, it's part of the build.

-- 
Tom

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2017-09-28 18:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 16:03 [PATCH] wic: Generate startup.nsh for EFI cases if none found Tom Rini
2017-09-28 15:47 ` Ed Bartosh
2017-09-28 17:44   ` Tom Rini
2017-09-28 17:46     ` Otavio Salvador
2017-09-28 17:49       ` Tom Rini
2017-09-28 17:57         ` Otavio Salvador
2017-09-28 17:59           ` Tom Rini
2017-09-28 18:01             ` Otavio Salvador
2017-09-28 18:04               ` Tom Rini [this message]
2017-09-29 11:27     ` Ed Bartosh
2017-09-29 12:35       ` Tom Rini
2017-09-29 13:44         ` Ed Bartosh
2017-09-29 13:50           ` Tom Rini

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=20170928180442.GR3112@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=chris_larson@mentor.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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