From: Ben Schneider <ben@bens.haus>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Regressions <regressions@lists.linux.dev>,
Linux Efi <linux-efi@vger.kernel.org>,
Stable <stable@vger.kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>
Subject: Re: [REGRESSION] boot fails for EFI boot stub loaded by u-boot
Date: Sat, 21 Oct 2023 02:07:56 +0200 (CEST) [thread overview]
Message-ID: <NhEYpWg--3-9@bens.haus> (raw)
In-Reply-To: <Nh8pThy--3-9@bens.haus>
Oct 20, 2023, 01:25 by ben@bens.haus:
> Oct 19, 2023, 07:21 by heinrich.schuchardt@canonical.com:
>
>> Compiling upstream U-Boot's qemu_arm64_defconfig yields lib/efi_loader/dtbdump.efi. If you run this instead of the kernel, you can write the device-tree as it is passed in a configuration table to the ESP.
>>
> I compiled and ran this fine, but I was unable to save the device tree. I suspect this is because the program searches for an ESP, and there is none on the device. U-boot was compiled with support to load directly from an ext4 filesystem so I didn't bother setting one up. I will work on it.
>
Hi Heinrich, I loaded dtbdump.efi from a FAT32 formatted partition with type EFI System, but attempts to run the save command return "Failed to open simple file system protocol". Sorry if there is something else I am missing.
Ben
next prev parent reply other threads:[~2023-10-21 0:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 1:18 [REGRESSION] boot fails for EFI boot stub loaded by u-boot Ben Schneider
2023-10-18 8:34 ` Ard Biesheuvel
2023-10-18 9:17 ` Heinrich Schuchardt
2023-10-18 9:29 ` Ilias Apalodimas
2023-10-19 1:51 ` Ben Schneider
2023-10-19 7:21 ` Heinrich Schuchardt
2023-10-20 1:25 ` Ben Schneider
2023-10-21 0:07 ` Ben Schneider [this message]
2023-10-22 10:17 ` Heinrich Schuchardt
2024-01-31 18:00 ` Ben Schneider
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=NhEYpWg--3-9@bens.haus \
--to=ben@bens.haus \
--cc=ardb@kernel.org \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linux-efi@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.