Ben Westover c10a3ce73b parse.bootimg: Separate kernel and ramdisk MediaTek headers ... Currently, pmbootstrap checks if either the kernel or the ramdisk in a boot.img contains the MediaTek header, and if one does, it assumes both do. It hardcodes the label KERNEL for the kernel and ROOTFS for the ramdisk. My Amazon Echo Dot (gen 2) has a boot.img where only the kernel has the header, but not the ramdisk. These changes (as well as those in my new boot-deploy MR) account for that situation (and any possible label an image has) by splitting bootimg_mtk_mkimage into two variables for the kernel and the ramdisk labels. Reviewed-by: Oliver Smith <ollieparanoid@postmarketos.org> Link: https://lists.sr.ht/~postmarketos/pmbootstrap-devel/patches/46351		2023-11-13 09:30:24 +01:00
..
__init__.py	Bump copyright to 2023	2023-01-22 19:18:06 +01:00
binutils.py	aportgen/binutils: set pmOS bugurl	2023-05-25 09:45:07 +02:00
busybox_static.py	aportgen: use pmb.build.init_abuild_minimal	2023-06-15 08:30:54 +02:00
core.py	Bump copyright to 2023	2023-01-22 19:18:06 +01:00
device.py	parse.bootimg: Separate kernel and ramdisk MediaTek headers	2023-11-13 09:30:24 +01:00
gcc.py	Bump copyright to 2023	2023-01-22 19:18:06 +01:00
grub_efi.py	aportgen: use pmb.build.init_abuild_minimal	2023-06-15 08:30:54 +02:00
linux.py	pmb.aportgen.linux: Depend on findutils	2023-03-12 17:20:55 +01:00
musl.py	aportgen: use pmb.build.init_abuild_minimal	2023-06-15 08:30:54 +02:00