release: arm64: Use loader.efi as bootaa64.efi for RPI3 and PINE64
boot1.efi have some trouble to read MBR partitions, it needs them to be aligned a certain way while loader.efi can cope with them either way. We want to switch to loader.efi as the main efi loader everywhere, it seems that arm64 using MBR partition will be the guinea pig. Tested On: RPI3, Pine64 Reviewed by: imp Approved by: gjb
This commit is contained in:
parent
15f8acc53f
commit
785724755a
@ -34,7 +34,7 @@ arm_install_uboot() {
|
||||
BOOTFILES="$(chroot ${CHROOTDIR} realpath ${BOOTFILES})"
|
||||
|
||||
chroot ${CHROOTDIR} mkdir -p ${FATMOUNT}/EFI/BOOT
|
||||
chroot ${CHROOTDIR} cp -p ${BOOTFILES}/efi/boot1/boot1.efi \
|
||||
chroot ${CHROOTDIR} cp -p ${BOOTFILES}/efi/loader/loader.efi \
|
||||
${FATMOUNT}/EFI/BOOT/bootaa64.efi
|
||||
chroot ${CHROOTDIR} touch ${UFSMOUNT}/firstboot
|
||||
sync
|
||||
|
@ -54,7 +54,7 @@ arm_install_uboot() {
|
||||
BOOTFILES="$(chroot ${CHROOTDIR} realpath ${BOOTFILES})"
|
||||
|
||||
chroot ${CHROOTDIR} mkdir -p ${FATMOUNT}/EFI/BOOT
|
||||
chroot ${CHROOTDIR} cp -p ${BOOTFILES}/efi/boot1/boot1.efi \
|
||||
chroot ${CHROOTDIR} cp -p ${BOOTFILES}/efi/loader/loader.efi \
|
||||
${FATMOUNT}/EFI/BOOT/bootaa64.efi
|
||||
chroot ${CHROOTDIR} touch ${UFSMOUNT}/firstboot
|
||||
sync
|
||||
|
Loading…
Reference in New Issue
Block a user