All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH] efi_loader: improve detection of ESP for storing UEFI variables
Date: Mon, 9 Nov 2020 15:46:14 +0100	[thread overview]
Message-ID: <504f143a-74a5-255a-1d9a-eec819ed0fad@gmx.de> (raw)
In-Reply-To: <87imaed2dt.fsf@cjr.nz>

On 09.11.20 15:35, Paulo Alcantara wrote:
> Mark Kettenis <mark.kettenis@xs4all.nl> writes:
>
>> The OpenBSD installation media for armv7 and arm64 use a FAT partition
>> of type 0x0c because the Raspberry Pi firmware doesn't support 0xef.
>> This allows us to have a single FAT partition with the Raspberry Pi
>> firmware, U-Boot and /EFI/BOOT/BOOT{ARCH}.EFI.
>
> Yeah, it is the same partition type that my openSUSE Tumbleweed image
> has and everything boots fine on rpi4.
>
> My only problem with not having the partition type of 0xef in MBR is
> that my UEFI variables (/ubootefi.var) could not be loaded because
> U-Boot did not detect an ESP to either read or store them, but the UEFI
> boot worked regardless.
>

Hello Matthias,

While SUSE generally recommends to have an ESP partition with partition
type 0xef this is not so on the Raspberry images, e.g.
http://download.opensuse.org/ports/aarch64/tumbleweed/appliances/openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64.raw.xz

Device                                                 Boot   Start
End Sectors  Size Id Type
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64.raw1         2048
133119  131072   64M  c W95 FAT32 (LBA)
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64.raw2       133120
1157119 1024000  500M 82 Linux swap / Solaris
openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64.raw3      1157120
4610014 3452895  1.6G 83 Linux

Why is SUSE not using a separate ESP partition mounted as /boot/efi here?

The mail thread starts here:
https://lists.denx.de/pipermail/u-boot/2020-November/432223.html

Best regards

Heinrich

  reply	other threads:[~2020-11-09 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-08 23:58 [PATCH] efi_loader: improve detection of ESP for storing UEFI variables Paulo Alcantara
2020-11-09 10:02 ` Heinrich Schuchardt
2020-11-09 13:24   ` Paulo Alcantara
2020-11-09 13:51     ` Mark Kettenis
2020-11-09 14:35       ` Paulo Alcantara
2020-11-09 14:46         ` Heinrich Schuchardt [this message]
2020-11-09 14:36       ` Heinrich Schuchardt
2020-11-09 17:08         ` Mark Kettenis
2020-11-14  4:56           ` Heinrich Schuchardt
2020-11-16  5:02             ` Jonathan Gray
2020-11-09 13:58     ` Heinrich Schuchardt

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=504f143a-74a5-255a-1d9a-eec819ed0fad@gmx.de \
    --to=xypron.glpk@gmx.de \
    --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 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.