Its not immediately apparent that more than one install target could be
available. With this change we list the available devices up front then
prompt the user for which one to use, reducing confusion.
Fixes [YOCTO #9919].
Signed-off-by: California Sullivan <california.l.sulli...@intel.
to fit the functionality or update the
functionality to fit what the docs have been claiming. I'm also not sure
if I described the current functionality adequetly, so a look over this
and some feedback would be appreciated.
Thanks,
Cal Sullivan
California Sullivan (2):
sysvinit-inittab_2.88dsf.bb
to be documented.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
documentation/ref-manual/ref-variables.xml | 12
meta/conf/documentation.conf | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/documentation/ref-manu
#9440].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
b/meta/recipes-core/sy
It can take a bit for USB devices to be detected, so if a USB device is
your rootfs and you don't set rootwait you will most likely get a kernel
panic. Fix this by adding rootwait to the kernel command line on
installation.
Fixes [YOCTO #9462].
Signed-off-by: California Sullivan
#9440].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/sysvinit/sysvinit-inittab_2.88dsf.bb
b/meta/recipes-core/sy
free to update
it however you see fit. I'm not the best writer and I'm not confident
the description I gave is sufficient.
Thanks,
Cal Sullivan
California Sullivan (2):
sysvinit-inittab_2.88dsf.bb: Allow aliasing with SERIAL_CONSOLES_CHECK
documentation/ref-manual: Update SERIAL_CONSOLES_CHECK
to be documented.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
documentation/ref-manual/ref-variables.xml | 12
meta/conf/documentation.conf | 2 +-
2 files changed, 9 insertions(+), 5 deletions(-)
diff --git a/documentation/ref-manu
These errors can't be fixed without adding the firmware to the initramfs
and building it into the kernel, which we don't want to do for
genericx86-64. Since graphics still work acceptably without the firmware
blobs, just ignore the errors for that MACHINE.
Signed-off-by: California Sullivan
This error has occurred on the MinnowBoard Max and Turbot since its
inception. It supposedly indicates a non-working SD card reader, but
ours works fine. Whitelist the error.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py | 1 +
These errors have been occuring since the introduction of the 4.4
kernel with no apparent functionality loss. Whitelist for now.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py | 2 ++
1 file changed, 2 insertions(+)
diff --git
The kernel being built should match what the recipe claims it is
building. This function ensures that happens for anyone using
LINUX_VERSION as they should. As it will likely break outside kernels
not using LINUX_VERSION, only enable the function for linux-yocto for
now.
Signed-off-by: California
.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
The only change from V1 to V2 is the updated commit message, changing
AUTOINC to AUTOREV and adding the blurb about impacting outside recipes.
I also agree with Richard in that this is a significant functionality change
and
by default so that it is not both
opt-in and opt out.
Set the opt-out variable in linux-yocto-dev, fixing the issue with
AUTOINC.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/kernel.bbclass | 8 +++-
meta/recipes-kernel/linux/linux
BSPs for platforms using UEFI, such as meta-intel, would like to have
this more widely available for future support enhancements.
This is a direct copy of the recipe from meta-openembedded/meta-oe.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
We are
kernels. Remove
note about effecting all kernels.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/kernel.bbclass | 6 +-
meta/recipes-kernel/linux/linux-yocto-dev.bb | 1 +
2 files changed, 6 insertions(+), 1 deletion(-)
diff
(e.g., -rc4)
* Cleaned up version string building
Fixes [YOCTO #6767].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/kernel.bbclass | 30 ++
meta/recipes-kernel/linux/linux-yocto.inc | 1 +
2 files chang
option we would have to enable EXPERT and
DEBUG_KERNEL, which we don't want. Instead just whitelist it on all
x86 MACHINEs.
Fixes [YOCTO #10261].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py | 1 +
1 file changed, 1 insertion(+)
MACHINE builds.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.1.bbappend | 3 +++
meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.4.bbappend | 3 +++
2 files changed, 6 insertions(+)
diff --git a/meta-yocto-bsp/r
Trying to start getty on a non-existent console will spew I/O errors
into auth.log on some hardware. Avoid this behavior by checking that
ttyS0 is a console that exists.
Fixes [YOCTO #10291].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta-yocto-bsp/conf/m
The NUC6 firmware tells the kernel to try and initialize an embedded
DisplayPort it does not have, causing this warning. Its harmless, so
just whitelist it.
Fixes [YOCTO #9434].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py |
"qemux86-64" for
example, that the system is x86-64, so this is unlikely to cause any
new issues while preserving some peoples' old workflows.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
scripts/runqemu | 20 ++--
1 file changed, 10 i
This was already whitelisted, but the 4.8 kernel changed the error
message, causing it to get caught by parselogs again.
Fixes [YOCTO #10494].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py | 1 +
1 file changed, 1 insertion(+)
, meaning we get errors for 24 and 23.
Filter out iwlwifi firmware load error messages, as they are not
necessarily indicative of real problems.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/parselogs.py | 1 +
1 file changed, 1 insertion(+)
diff
The Joule is very new hardware and there is ongoing kernel and firmware
work to fix these issues, which will be available in future kernel and
firmware releases. In the meantime, don't clog QA reports.
[YOCTO #10611]
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
Image creation seems to always grab ${type} (usually bzImage), even if
we specifically use INITRAMFS_IMAGE_BUNDLE to create a bundled
initramfs/kernel. Work around this by linking ${type}.initramfs to
${type} as a final step when it exists.
Signed-off-by: California Sullivan <california.l.su
This was already whitelisted, but the 4.8 kernel changed the error
message, causing it to get caught by parselogs again.
Fixes [YOCTO #10494].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
Signed-off-by: Ross Burton <ross.bur...@intel.com>
(cherry picked
Some out of tree modules require the scripts for configuration. For
example, backport-iwlwifi.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/module.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/module.bbc
Version 3.0.6 fixes a failure when using the pxe headers and allows us
to drop the explicit fall through patch as it was fixed upstream.
Other patches were rebased on top of the new version.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
...plicit-fall-thro
usecs
[ 13.090987] Bluetooth: hci0: Waiting for device to boot
[ 13.101958] Bluetooth: hci0: Device booted in 10818 usecs
Bluetooth does successfully come up and the firmware is loaded. This
behavior is consistent across all kernels I've tested.
[YOCTO #10628].
Signed-off-by: California
won't cause any functional issues.
[YOCTO #10110].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/lib/oeqa/runtime/cases/parselogs.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/lib/oeqa/runtime/cases/parselogs.py
b/meta/lib/oeqa/runtime
-by: California Sullivan <california.l.sulli...@intel.com>
---
NOTE: for the selftests to be fixed, the patch
"initramfs-framework/setup-live: remove superfluous break" needs to be
merged as well.
meta/recipes-core/initrdscripts/initramfs-framework/setup-live | 2 +-
1 file changed, 1
This causes us to fall out of the module setup/run loop in the base init
script should "root=" be defined, causing a boot failure.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/recipes-core/initrdscripts/initramfs-framework/setup-live | 2 --
1
for root=/dev/ram0 as well.
See: https://www.kernel.org/doc/html/v4.11/admin-guide/initrd.html#operation
This fixes the issue where the new initramfs-framework scripts would not
boot live images that use grub or syslinux bootloaders.
Signed-off-by: California Sullivan <california.l.su
Using += makes it difficult to remove. Soft-set with ?= instead.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/conf/machine/include/x86-base.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/conf/machine/include/x86-base.inc
b/met
The secondary EFI partition is used when booting in EFI mode, and
without the configuration data we don't get any boot targets.
Partial fix to [YOCTO #11503].
(From OE-Core master rev: 84aa7a00810e135fdad3f77bdb1da7d1f5fb8627)
Signed-off-by: California Sullivan <california.l.sulli...@intel.
The secondary EFI partition is used when booting in EFI mode, and
without the configuration data we don't get any boot targets.
Partial fix to [YOCTO #11503].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
meta/classes/systemd-boot.bbclass | 1 +
1 file chan
ed-off-by: Stefan Agner <stefan.ag...@toradex.com>
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
Hi Stefan,
In interest of getting this into 2.4 (freezes Monday, and it turns out
we also need this latest bump), I went ahead and fixed it up as per
Ross' suggesti
-framework
* add allarch to setup-live and install-efi modules, as they're just
shell scripts
v3 changes:
* set PR of new recipes to 4, as the name of the packages they build
is the same as when they were part of the main recipe.
Signed-off-by: California Sullivan <california.l.su
-framework
* add allarch to setup-live and install-efi modules, as they're just
shell scripts
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
I think I agree with Otavio on the allarch discussion. Setup-live at the
very least is applicable to everything, and while i
in the new module recipes to avoid breaking
package feeds.
Fixes [YOCTO #12024].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
Reading the commit message this maybe should be split into multiple
patches, but since they're issues caused by the taking the v1 version
When bootparam_root was empty the if statement would resolve into
invalid syntax instead of short circuiting after the -z, causing a boot
failure.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
I stupidly didn't test an empty root parameter with my previous
Having these the initramfs-framework recipe forced initramfs-framework
users to build several tools they didn't need, and made it more
difficult to declare the recipe as allarch.
Fixes [YOCTO #12024].
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../initrds
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
There is no need to maintain two of the exact same files.
Signed-off-by: California Sullivan <california.l.sulli...@intel.com>
---
.../initramfs-framework/install-efi.sh | 276 -
.../initramfs-module-install-efi_1.0.bb| 6 +-
2 files chan
, whereas the first two are just minor
improvements to the install-efi module.
California Sullivan (3):
initramfs-module-install-efi: point to original copy and delete new
file
initramfs-module-install-efi: update summary
initramfs-framework: add install module
.../initramfs-framework
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
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:
, 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(-)
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
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
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
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
.
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
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
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>
---
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
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
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
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
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
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
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
-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
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
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
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 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
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_
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
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
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
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
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
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
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
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
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
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
.
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(-)
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 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
1 - 100 of 145 matches
Mail list logo
