From: Jonathan Gray <jsg@jsg.id.au>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] efi_loader: Add test to boot OpenBSD's efi bootloader
Date: Thu, 10 Aug 2017 13:43:24 +1000 [thread overview]
Message-ID: <20170810034324.GA19375@largo.jsg.id.au> (raw)
In-Reply-To: <CAF6AEGu8_UE=USuqb6vc-Z75dT=5EyjzhtMKy5p-4bq70qbvaA@mail.gmail.com>
On Sun, Aug 06, 2017 at 03:06:17PM -0400, Rob Clark wrote:
> On Sun, Aug 6, 2017 at 2:54 PM, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> >> From: Rob Clark <robdclark@gmail.com>
> >> Date: Sun, 6 Aug 2017 12:10:28 -0400
> >>
> >> Signed-off-by: Rob Clark <robdclark@gmail.com>
> >> ---
> >> Kinda works, but since we don't have an 'exit' command like grub, we
> >> have to reboot, which leaves the "board" in a bad state (I guess,
> >> since the next test fails). I haven't tackled the travis bits to get
> >> travis to download OpenBSD's bootloader, or other little details like
> >> that.
> >
> > What does the grub "exit" command do? Simply call EFI_BOOT_SERVICE.Exit()?
> > Wouldn't be too difficult for me to add a command that does this.
>
> Yeah, I think just calls BS->Exit().. that would be quite useful.
Mark committed the change for this and snapshots now have "machine exit"
and "machine poweroff".
https://ftp.openbsd.org/pub/OpenBSD/snapshots/armv7/BOOTARM.EFI
https://ftp.openbsd.org/pub/OpenBSD/snapshots/arm64/BOOTAA64.EFI
next prev parent reply other threads:[~2017-08-10 3:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 16:10 [U-Boot] [RFC] efi_loader: Add test to boot OpenBSD's efi bootloader Rob Clark
2017-08-06 18:54 ` Mark Kettenis
2017-08-06 19:06 ` Rob Clark
2017-08-10 3:43 ` Jonathan Gray [this message]
2017-08-10 10:41 ` Rob Clark
2017-08-07 16:25 ` Stephen Warren
2017-08-11 9:46 ` Alexander Graf
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=20170810034324.GA19375@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=u-boot@lists.denx.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