[meta-intel] [PATCH RFC 0/4] First pass at combo app and secure boot support

[Patrick Ohly]

On Fri, 2017-06-09 at 18:30 -0700, California Sullivan wrote:
> While its possible to use wic with it thanks to the uefiapp_deploy
> function, the init scripts in the initramfs we currently ship are made
> for live images, and will attempt to mount and boot a rootfs.img, which
> will fail.

Why does it fail? Aside from the different content of bootx64.efi, I'd
expect the rest of the disk image to be unchanged, so I can't imagine
why it might fail.

> The second issue is that this class is dependant on an INTIRD_IMAGE.
> This means that the class cannot be added via IMAGE_CLASSES in a global
> context (such as local.conf), as it would create a circular dependency.
> So, in order to apply this while using wic alone, we would need to
> conditionally inherit it on every non-initrd/initramfs image target
> through bbappends, which would be a little messy. I've already tried
> that workaround successfully, but I'm currently brainstorming solutions
> looking for something cleaner.

This is presumably a result of changing INITRD_LIVE? It might be better
to not rely or affect image-live.bbclass at all.

Also note that the comment about that particular change is about aspects
("copying to rootfs", "swupd bundle support") which might not be
applicable anymore.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.