uced a new
INITRAMFS_SCRIPTS variable to the core-image-minimal-initramfs recipe.
This variable makes the recipe look much cleaner, and also allows easier
replacement or additions to the scripts.
Fixes [YOCTO #10987].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
Di
to be installed, we actually get a smaller boot partition with less
wasted space.
Also add VIRTUAL-RUNTIME_base-utils to RDEPENDS where these scripts are
used, as they're needed for the du command.
[YOCTO #12583].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
* v
to be installed, we actually get a smaller boot partition with less
wasted space.
[YOCTO #12583].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 15 +--
meta/recipes-core/initrdscripts/file
et bzImage as the default. Others get zImage as per
meta/conf/documentation.conf.
Also set KERNEL_IMAGETYPES, as we will eventually be switching away from
KERNEL_IMAGETYPE.
Thanks to Andre McCurdy <armccu...@gmail.com> for the arch defaults
part.
Signed-off-by: California Sullivan <california.l
PES, as we will eventually be switching away from
KERNEL_IMAGETYPE.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 1 -
meta/classes/live-vm-common.bbclass | 2 --
meta/classes/syslinux.bbclass
Debian and Fedora both carry this patch, and the xf86-video-modesetting
driver seems better on recent hardware.
As an example, on a NUC6CAYS, the x11perf -aa10text and -rgb10text tests
see around a 20x increase.
[YOCTO #12019]
[YOCTO #12390]
Signed-off-by: California Sullivan
Most distros have switched to this, and we're seeing better results in
some areas as well. E.g., on a NUC6CAYS the x11perf -aa10text and
-rgb10text results see a 20x increase.
[YOCTO #12019].
[YOCTO #12590].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
met
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbc
Using --exclude-path and a wks.in file we can create an image that takes
the /boot/ directory for the boot partition, has an empty /boot/
directory in the rootfs partition. The boot partition gets mounted to
/boot/ after startup.
Signed-off-by: California Sullivan <california.l.sulli...@intel.
ll search for common kernel names to copy into our boot
directory.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/recipe
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
meta/c
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 31 ++
1 file changed, 31 insertions(+)
create mode 10064
Since kernels will not necessarily be installed as vmlinuz anymore,
don't assume that's its name for either the bootloader config or the
copy of the kernel.
Also, allow installing multiple kernels by searching for common kernel
names.
Signed-off-by: California Sullivan <california.l.su
to change.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot-cfg.bbclass | 5 -
1 file changed, 5 deletions(-)
diff --git a/meta/classes/systemd-boot-cfg.bbclass
b/meta/classes/systemd-boot-cfg.bbclass
index 360c86cbd34..107758548c6
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/s
The bootloaders depend on these to be functional in the non-deploy case,
but changes in them don't require rebuilding of the packages.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/conf/layer.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/met
to change.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 6 --
1 file changed, 6 deletions(-)
diff --git a/meta/classes/grub-efi-cfg.bbclass
b/meta/classes/grub-efi-cfg.bbclass
index 85173c91fc3..d2226af97a7 100644
--- a/meta/c
Simple test case that adds 'efi' to MACHINE_FEATURES, sets WKS_FILE to
"efi-bootdisk.wks.in", installed required boot items, and attempts to
boot the wic image.
Quick check to make sure that the feature actually works.
Signed-off-by: California Sullivan <california.l.sulli
This part is useful on its own, whereas the whole class together is
specific for image-live.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../{grub-efi.bbclass => grub-efi-cfg.bbclass} | 40 ---
meta/classes/grub-efi.bbclass
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 2 +-
meta/recipes-bsp/grub/grub-efi_2.02.bb | 34 +++--
2 files c
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/conf/distro/include/maintainers.inc | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 50392487903..ba5e6137e77
.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
b/meta/recipes-core/packagegroups/packagegrou
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
eneric EFI boot partition.
V3 changes:
* Autobuilder testing revealed two failing tests with this patchset:
https://autobuilder.yocto.io/builders/nightly-oe-selftest/builds/858/steps/Running%20oe-selftest/logs/stdio
Patches 19-21 fix these.
California Sullivan (21):
grub-efi.bbclass: s
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 29 +
1 file changed, 29 inse
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/s
Simple test case that adds 'efi' to MACHINE_FEATURES, sets WKS_FILE to
"efi-bootdisk.wks.in", installed required boot items, and attempts to
boot the wic image.
Quick check to make sure that the feature actually works.
Signed-off-by: California Sullivan <california.l.sulli
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass
The bootloaders depend on these to be functional in the non-deploy case,
but changes in them don't require rebuilding of the packages.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/conf/layer.conf | 2 ++
1 file changed, 2 insertions(+)
diff --git a/met
ll search for common kernel names to copy into our boot
directory.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/recipe
Since kernels will not necessarily be installed as vmlinuz anymore,
don't assume that's its name for either the bootloader config or the
copy of the kernel.
Also, allow installing multiple kernels by searching for common kernel
names.
Signed-off-by: California Sullivan <california.l.su
Using --exclude-path and a wks.in file we can create an image that takes
the /boot/ directory for the boot partition, has an empty /boot/
directory in the rootfs partition. The boot partition gets mounted to
/boot/ after startup.
Signed-off-by: California Sullivan <california.l.sulli...@intel.
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbc
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 31 ++
1 file changed, 31 insertions(+)
create mode 10064
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
b/meta/recipes-core/packagegroups/packagegrou
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
meta/c
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
idable. Woops.
* Fix fixup in 'systemd-boot: add package that installs to boot' that
belonged in the systemd-bootconf recipe patch.
* Add -bootconf recipes to SIGGEN_EXCLUDE_SAFE_RECIPE_DEPS to avoid
rebuilding grub-efi/systemd-boot when not necessary.
* Add basic test case that leverages the gen
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 2 +-
meta/recipes-bsp/grub/grub-efi_2.02.bb | 34 +++--
2 files c
This part is useful on its own, whereas the whole class together is
specific for image-live.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../{grub-efi.bbclass => grub-efi-cfg.bbclass} | 40 ---
meta/classes/grub-efi.bbclass
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 29 +
1 file changed, 29 inse
Since kernels will not necessarily be installed as vmlinuz anymore,
don't assume that's its name for either the bootloader config or the
copy of the kernel.
Also, allow installing multiple kernels by searching for common kernel
names.
Signed-off-by: California Sullivan <california.l.su
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/s
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 29 ++
1 file changed, 29 insertions(+)
create mode 10064
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbc
ll search for common kernel names to copy into our boot
directory.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/recipe
Using --exclude-path and a wks.in file we can create an image that takes
the /boot/ directory for the boot partition, has an empty /boot/
directory in the rootfs partition. The boot partition gets mounted to
/boot/ after startup.
Signed-off-by: California Sullivan <california.l.sulli...@intel.
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
meta/c
.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
b/meta/recipes-core/packagegroups/packagegrou
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 2 +-
meta/recipes-bsp/grub/grub-efi_2.02.bb | 34 +++--
2 files c
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
This part is useful on its own, whereas the whole class together is
specific for image-live.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../{grub-efi.bbclass => grub-efi-cfg.bbclass} | 40 ---
meta/classes/grub-efi.bbclass
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 29 +
1 file changed, 29 inse
branch available to pull from here:
https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=clsulliv/image-creation-sda
A previous iteration including the UUID stuff that's not included here
is available at clsulliv/image-creation-exclude-path
Thanks,
Cal
California Sullivan (16):
g
Command failed.
Press any key to continue...
Fix this by setting HOSTLDFLAGS to ${BUILD_LDFLAGS} in our
'make menuconfig' command.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/kernel.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/c
-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../cryptodev/cryptodev-module_1.9.bb | 1 +
.../0001-ioctl.c-Fix-build-with-linux-4.13.patch | 49 ++
2 files changed, 50 insertions(+)
create mode 100644
meta/recipes-kernel/cryptodev/file
ur...@intel.com>
(cherry picked from commit ecad98a0ffe41d8cc8890d16be09e4b604a1e192)
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../initrdscripts/initramfs-module-install-efi_1.0.bb | 3 ---
meta/recipes-core/initrdscripts/initramfs-module-install_
The grub_version variable was calling 'grub-install -v' (verbose) instead
of 'grub-install -V' (version) causing unexpected failures.
Fixes bug [YOCTO #12111].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
Signed-off-by: Ross Burton <ross.bur...@intel.com>
(c
nodes for a short duration.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
Signed-off-by: Ross Burton <ross.bur...@intel.com>
(cherry picked from commit 9daafd49b448122e35d67a1637ce2212793a4dc5)
Signed-off-by: California Sullivan <california.l.sulli...@intel
There is no need to maintain two of the exact same files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
Signed-off-by: Ross Burton <ross.bur...@intel.com>
(cherry picked from commit 49ba882be9e28a51651a543779e6f02d33861393)
Signed-off-by: Califor
The non-EFI counterpart for installation was previously missing for
initramfs-framework. This simply puts the normal install script in the
correct location for initramfs-framework to make use of it.
Partial fix for [YOCTO #12346].
Signed-off-by: California Sullivan <california.l.su
California Sullivan (5):
initramfs-module-install-efi: point to original copy and delete new
file
initramfs-module-install-efi: update summary
initramfs-framework: add install module
init-install: fix grub-install command
install*.sh: add short sleep after parted commands
Martin Jansa (1
Note that this is an installation option for EFI systems.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
Signed-off-by: Ross Burton <ross.bur...@intel.com>
(cherry picked from commit 366ddd22245a72df4c8e561761c6df8a6654bba6)
Signed-off-by: Califor
We can't guarantee vmlinuz anymore. Use KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot-cfg.bbclass | 6 +-
meta/classes/systemd-boot.bbclass | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
diff
With the postprocess command and installation into /boot/ in place, we
can use wic to create an EFI-compatible image without it having any
knowledge of the kernel or bootloader.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
scripts/lib/wic/canned-w
We can't guarantee the kernel will be named vmlinuz anymore. Use
KERNEL_IMAGETYPE instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/syslinux.bbclass | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/meta/classes/syslinux.bbc
This class is useful on its own and can be used to create configuration
recipes.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
...stemd-boot.bbclass => systemd-boot-cfg.bbclass} | 57 --
meta/classes/systemd-boot.bbclass
This way we could theoretically support multiple bootloaders, and we
keep the convention of boot(x64|ia32).
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
ll search for common kernel names to copy into our boot
directory.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 15 ++-
1 file changed, 10 insertions(+), 5 deletions(-)
diff --git a/meta/recipe
This makes use of the grub-efi-cfg bbclass that was split out to create
a grub.cfg file just like the old one.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-bootconf_1.00.bb | 30 +
1 file changed, 30 inse
This gives the class access to the DISK_SIGNATURE_UUID variable.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/image.bbclass | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
index ec940
Previously this wasn't needed because the kernel was added at image
creation time to the boot partition. Now that the boot partition is
created from the /boot/ partition of the rootfs, it needs to be
installed there.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/packagegroups/packagegroup-core-boot.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recipes-core/packagegroups/packagegroup-core-boot.bb
b/meta/recipes-core/packagegroups/packagegrou
EFI systems need their /boot/ directory in its own partition. By
splitting it into its own directory like this, we avoid /boot/ ending up
in the primary rootfs, and can easily create the EFI partition from the
IMAGE_BOOTFS directory.
Signed-off-by: California Sullivan <california.l.su
I couldn't find anywhere it was being used, and in trying to use it it
just spit out an error.
It now generates a random UUID and puts it in the deploy dir for
consumption.
Also use DISK_SIGNATURE_UUID for the replacement function, since that
is user-overridable.
Signed-off-by: California
Rather than renaming the kernel to vmlinuz and assuming the name is
vmlinuz in the grub.cfg, copy to ${KERNEL_IMAGETYPE} and also use that
value in the grub.cfg file.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/grub-efi-cfg.bbclass | 4 +++-
meta/c
If the EFI_PROVIDER is systemd-boot, install as boot(x64|ia32) as per
convention. If its not the EFI_PROVIDER, install as
systemd-boot(x64|ia32), as to not collide with other possible
bootloaders.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/s
Since /boot/ will be recipe/package controlled now we can't just deploy.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-bsp/grub/grub-efi_2.02.bb | 32 +---
1 file changed, 25 insertions(+), 7 deletions(-)
diff --git
Reuses our systemd-boot-cfg bbclass to generate systemd-boot
configuration files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/systemd/systemd-bootconf_1.00.bb | 31 ++
1 file changed, 31 insertions(+)
create mode 10064
, so please
any feedback is welcome.
Thanks,
Cal
California Sullivan (18):
fs-uuid.bbclass: rewrite get_fs_uuid function
image.bbclass: Add fs-uuid bbclass
grub-efi.bbclass: split out configuration portion
grub: create recipe for configuration
grub-efi: install to /boot/
grub-efi
I can't find VM_DEFAULT_KERNEL used anywhere else, and we should not be
statically installing the kernel as vmlinuz.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/live-vm-common.bbclass | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
uced a new
INITRAMFS_SCRIPTS variable to the core-image-minimal-initramfs recipe.
This variable makes the recipe look much cleaner, and also allows easier
replacement or additions to the scripts.
Fixes [YOCTO #10987].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
m
nodes for a short duration.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
v2: sleep conditionally for up to three seconds instead of one second
unconditionally. This makes it so if the device nodes are available
immediately, people don't have to wait, but a system
The grub_version variable was calling 'grub-install -v' (verbose) instead
of 'grub-install -V' (version) causing unexpected failures.
Fixes bug [YOCTO #12111].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install.
before doing the mkfs
commands.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/files/init-install-efi.sh | 2 ++
meta/recipes-core/initrdscripts/files/init-install.sh | 2 ++
2 files changed, 4 insertions(+)
diff --git a/meta/r
The non-EFI counterpart for installation was previously missing for
initramfs-framework. This simply puts the normal install script in the
correct location for initramfs-framework to make use of it.
Partial fix for [YOCTO #12346].
Signed-off-by: California Sullivan <california.l.su
The non-EFI counterpart for installation was previously missing for
initramfs-framework. This simply puts the normal install script in the
correct location for initramfs-framework to make use of it.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
V2 changes:
The non-EFI counterpart for installation was previously missing for
initramfs-framework. This simply puts the normal install script in the
correct location for initramfs-framework to make use of it.
Partial fix for [YOCTO #12346].
Signed-off-by: California Sullivan <california.l.su
Note that this is an installation option for EFI systems.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-module-install-efi_1.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/meta/recipe
1 - 100 of 145 matches
Mail list logo
