On Fri, Mar 29, 2019 at 12:07:59AM +0000, Liu, Yongxin wrote: > > -----Original Message----- > > From: Tom Rini [mailto:[email protected]] > > Sent: Thursday, March 28, 2019 21:59 > > To: Liu, Yongxin > > Cc: [email protected] > > Subject: Re: [OE-core] [PATCH] wic/bootimg-efi.py: add new source > > parameter "initrd_rename" > > > > On Wed, Mar 27, 2019 at 06:37:42PM +0800, Yongxin Liu wrote: > > > > > When using initrd in bootloader configuration file, we may want the > > > name of initrd to be fixed. However, the actual name of initrd may > > > change and depend on distro/machine's name. "initrd_rename" > > > gives user a chance to rename initrd in final wic image. > > > > > > Signed-off-by: Yongxin Liu <[email protected]> > > > > I'm not nak'ing this patch, but I've long fixed this by just not using > > the "efi" plugin to make an EFI system and instead IMAGE_BOOT_FILES to > > say what goes where. There's a lot of cases bootimg-efi doesn't cover > > but are handled easily with IMAGE_BOOT_FILES. > > > Thanks Tom for your input. > > What I want to do is to copy > "${INITRD_IMAGE_LIVE}-${MACHINE}.${INITRAMFS_FSTYPES}" > to EFI boot partition and rename it to be "initrd", like > > /boot > ├── bzImage > ├── EFI > │ └── BOOT > │ ├── bootx64.efi > │ └── grub.cfg > ├── initrd > > "IMAGE_BOOT_FILES" is good to provide such function. > How about porting "IMAGE_BOOT_FILES" to bootimg-efi.py?
The only thing that bootimg-efi.py provides, in my mind, is auto-generation of a simplistic grub/systemd-boot config file. I also don't ever want that and just list the config files under IMAGE_BOOT_FILES as well. I really think we could drop bootimg-efi.py aside from the case where we don't have a config file for some reason (Stand-alone wic?) -- Tom
signature.asc
Description: PGP signature
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
