Skip to contentSkip to conversation

wic: move uboot/spls mountpoint to /boot/firmware

PATCH In review Bryan Brattlof 5 participants 10 messages Jul 21, 2022 – Sep 28, 2023

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 wic: move uboot/spls mountpoint to /boot/firmware

Currently out boards will auto-mount the sd-card's boot partition into the /boot folder, effectively hiding the kernel image and dtb files that are already there.

Move the boot partition mount point to /boot/firmware allowing access to both the bootloader binares and kernel images.

---
 wic/sdimage-2part.wks | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
wic/sdimage-2part.wks +1 -1
index 77d6f7b576aef..7567c4429a2eb 100644
@@ -2,5 +2,5 @@
 # long-description: Creates a partitioned SD card image for TI platforms.
 # Boot files are located in the first vfat partition with extra reserved space.
 
-part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
+part /boot/firmware --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
 part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 1024 --use-uuid
Signature · 1 line
2.17.1
#1 lore raw

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

Quoted 25 lines · Bryan Brattlof

Currently out boards will auto-mount the sd-card's boot partition into the /boot folder, effectively hiding the kernel image and dtb files that are already there.

Move the boot partition mount point to /boot/firmware allowing access to both the bootloader binares and kernel images.

---
 wic/sdimage-2part.wks | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
wic/sdimage-2part.wks +1 -1
index 77d6f7b576aef..7567c4429a2eb 100644
@@ -2,5 +2,5 @@
 # long-description: Creates a partitioned SD card image for TI platforms.
 # Boot files are located in the first vfat partition with extra reserved space.
 
-part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
+part /boot/firmware --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
 part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 1024 --use-uuid
Signature · 1 line
2.17.1
#2 lore raw

Hi Denys!

+Tom Rini

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

Thanks
~Bryan

Quoted 26 lines · Bryan Brattlof
Quoted 24 lines

Currently out boards will auto-mount the sd-card's boot partition into the /boot folder, effectively hiding the kernel image and dtb files that are already there.

Move the boot partition mount point to /boot/firmware allowing access to both the bootloader binares and kernel images.

---
 wic/sdimage-2part.wks | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
wic/sdimage-2part.wks +1 -2
index 77d6f7b576aef..7567c4429a2eb 100644
@@ -2,5 +2,5 @@
 # long-description: Creates a partitioned SD card image for TI platforms.
 # Boot files are located in the first vfat partition with extra reserved space.
 
-part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
+part /boot/firmware --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 1024 --extra-space 100M --use-uuid
 part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 1024 --use-uuid
-- 2.17.1
#3 lore raw
Quoted 17 lines · Bryan Brattlof

Hi Denys!

+Tom Rini

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

Quoted 5 lines

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Signature · 1 line
Tom
#4 lore raw

On July 22, 2022 thus sayeth Tom Rini:

Quoted 17 lines · Bryan Brattlof
Quoted 16 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

Quoted 8 lines
Quoted 2 lines

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

~Bryan

#5 lore raw
Quoted 27 lines · Bryan Brattlof

On July 22, 2022 thus sayeth Tom Rini:

Quoted 17 lines · Bryan Brattlof
Quoted 16 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

Quoted 8 lines
Quoted 2 lines

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Quoted 4 lines

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

Keep in mind this is a generic OE on 64bit Arm problem and not a TI specific problem. Where to mount the ESP should have a consistent default. And it should look like it does on an off the shelf distro.

Signature · 1 line
Tom
#6 lore raw
Quoted 28 lines · Tom Rini
Quoted 27 lines · Bryan Brattlof

On July 22, 2022 thus sayeth Tom Rini:

Quoted 25 lines · Bryan Brattlof
Quoted 13 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

Quoted 5 lines

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Quoted 9 lines
Quoted 4 lines

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

Keep in mind this is a generic OE on 64bit Arm problem and not a TI specific problem. Where to mount the ESP should have a consistent default. And it should look like it does on an off the shelf distro.

While not an exact ESP partition, we are working on making our boot partition as close as we can given ROM constraints.

I'm running into the problem now of updating kernel on a live system, would fail as we have mounted our boot partition over the rootfs boot/ directory, so new images are not installed to the right spot/partition.

Let's go with /boot/efi if that works for everyone.

Bryan, could you re-send this with that change and the same for sdimage-2part-efi.wks.in?

Andrew

Quoted 10 lines

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14912): https://lists.yoctoproject.org/g/meta-ti/message/14912
Mute This Topic: https://lists.yoctoproject.org/mt/92535778/3619733
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-ti/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

#7 lore raw
Quoted 42 lines · Andrew Davis
Quoted 28 lines · Tom Rini
Quoted 27 lines · Bryan Brattlof

On July 22, 2022 thus sayeth Tom Rini:

Quoted 25 lines · Bryan Brattlof
Quoted 13 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

Quoted 5 lines

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Quoted 9 lines
Quoted 4 lines

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

Keep in mind this is a generic OE on 64bit Arm problem and not a TI specific problem. Where to mount the ESP should have a consistent default. And it should look like it does on an off the shelf distro.

While not an exact ESP partition, we are working on making our boot partition as close as we can given ROM constraints.

Quoted 8 lines

I'm running into the problem now of updating kernel on a live system, would fail as we have mounted our boot partition over the rootfs boot/ directory, so new images are not installed to the right spot/partition.

Let's go with /boot/efi if that works for everyone.

Bryan, could you re-send this with that change and the same for sdimage-2part-efi.wks.in?

The only feedback I would provide here is to work with the ROM team to fix whatever constraints prevent an "ESP" itself from being used as this will hinder the long term viability of the processors being widely supported.

Signature · 1 line
Tom
#8 lore raw
Quoted 49 lines · Tom Rini
Quoted 48 lines · Andrew Davis
Quoted 28 lines · Tom Rini
Quoted 27 lines · Bryan Brattlof

On July 22, 2022 thus sayeth Tom Rini:

Quoted 25 lines · Bryan Brattlof
Quoted 13 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

Quoted 5 lines

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Quoted 9 lines
Quoted 4 lines

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

Keep in mind this is a generic OE on 64bit Arm problem and not a TI specific problem. Where to mount the ESP should have a consistent default. And it should look like it does on an off the shelf distro.

While not an exact ESP partition, we are working on making our boot partition as close as we can given ROM constraints.

I'm running into the problem now of updating kernel on a live system, would fail as we have mounted our boot partition over the rootfs boot/ directory, so new images are not installed to the right spot/partition.

Let's go with /boot/efi if that works for everyone.

Quoted 7 lines
Quoted 2 lines

Bryan, could you re-send this with that change and the same for sdimage-2part-efi.wks.in?

The only feedback I would provide here is to work with the ROM team to fix whatever constraints prevent an "ESP" itself from being used as this will hinder the long term viability of the processors being widely supported.

Haha, this debate has lasted so long that systemd-boot has standardized mounting the ESP partition to just /efi now [1].

[1] https://www.freedesktop.org/software/systemd/man/systemd-boot.html

Randolph

#9 lore raw

On September 28, 2023 thus sayeth Res Sapp:

Quoted 58 lines · Tom Rini
Quoted 49 lines · Andrew Davis
Quoted 48 lines · Tom Rini
Quoted 28 lines · Bryan Brattlof
Quoted 27 lines

On July 22, 2022 thus sayeth Tom Rini:

Quoted 25 lines · Bryan Brattlof
Quoted 13 lines

On July 21, 2022 thus sayeth Denys Dmytriyenko:

Quoted 3 lines

I don't think this is a correct solution, or maybe I'm not understanding the problem. Can you please elaborate a bit more on the problem?

I'm fairly new to yocto so I'm sure I've found the entirely wrong way to get what I wanted :)

After boot it appears /etc/fstab is setup to mount our vfat boot partition to the /boot directory currently holding the Image and dtbs. I guess because uboot has already thrown the kernel and dtb into ddr at this point only Anand was able to notice this.

Quoted 5 lines

My change should mount the vfat partition to /boot/firmware so we can access to both our spls and kernel binaries in /boot.

I'm also not sure what folder name to use here. It seem like there may be a standard to this? Would /boot/uboot be more correct?

So which SoCs are we talking about here? For the 64bit parts, the intention should be that the FAT partition on p1 be functional as the ESP. So that means mounting it to /boot/efi. But I'm not sure off-hand how that's being treated in upstream OE around the notion of making an image that's what a UEFI system expects.

Quoted 9 lines
Quoted 4 lines

Ideally this should be for all TI's K3 devices. I'm unfamiliar with the UEFI format and don't know if we currently follow it, however I like the idea of /boot/efi from what I googled. I also found raspian is using /boot/firmware. Could this be less of a standard than I think?

Keep in mind this is a generic OE on 64bit Arm problem and not a TI specific problem. Where to mount the ESP should have a consistent default. And it should look like it does on an off the shelf distro.

While not an exact ESP partition, we are working on making our boot partition as close as we can given ROM constraints.

I'm running into the problem now of updating kernel on a live system, would fail as we have mounted our boot partition over the rootfs boot/ directory, so new images are not installed to the right spot/partition.

Let's go with /boot/efi if that works for everyone.

Quoted 7 lines
Quoted 2 lines

Bryan, could you re-send this with that change and the same for sdimage-2part-efi.wks.in?

The only feedback I would provide here is to work with the ROM team to fix whatever constraints prevent an "ESP" itself from being used as this will hinder the long term viability of the processors being widely supported.

Quoted 4 lines

Haha, this debate has lasted so long that systemd-boot has standardized mounting the ESP partition to just /efi now [1].

[1] https://www.freedesktop.org/software/systemd/man/systemd-boot.html

Even systemd was having trouble trying to figure it out[2] ;)

I'll respin this today with /boot/efi

~Bryan

[2] https://github.com/systemd/systemd/pull/3757