| /rk3399_rockchip-uboot/lib/avb/libavb/ |
| H A D | avb_slot_verify.c | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|
| /rk3399_rockchip-uboot/include/ |
| H A D | android_image.h | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|
| H A D | image.h | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|
| /rk3399_rockchip-uboot/lib/avb/libavb_user/ |
| H A D | avb_ops_user.c | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|
| /rk3399_rockchip-uboot/common/ |
| H A D | image-android.c | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|
| H A D | android_bootloader.c | 2831711026f8edb3cc079d1d06cc58c32f154ca4 Fri Oct 21 08:26:01 UTC 2022 Joseph Chen <chenjh@rock-chips.com> android: avb: Add init_boot support
== init-boot:
This new init_boot partition contains the ramdisk the used to live in
the boot partition. The boot partition will no longer contain that
ramdisk.
init_boot use android v4 header and is mandory from Android-13.
== avb with unlock:
Don't process hash verify.
Go pre-loaded path: Loading vendor_boot and init_boot
directly to where they should be, while loading the
boot/recovery. The boot message tells like:
···
preloaded: distribute image from 'boot_a'
preloaded: distribute image from 'init_boot_a'
preloaded: distribute image from 'vendor_boot_a'
···
== avb with lock:
Process hash verify.
Go pre-loaded path: Loading full vendor_boot, init_boot and
boot/recovery one by one to verify, and distributing them to
where they should be by memcpy at last.
The three images share a large memory buffer that allocated
by sysmem_alloc(), it locate at high memory address that
just lower than SP bottom. The boot message tells like:
···
preloaded: full image from 'boot_a' at 0xe47f90c0 - 0xe7a4b0c0
preloaded: full image from 'init_boot_a' at 0xeaff90c0 - 0xeb2950c0
preloaded: full image from 'vendor_boot_a' at 0xe87f90c0 - 0xe9f6e0c0
···
Signed-off-by: Joseph Chen <chenjh@rock-chips.com>
Change-Id: I9c8428eb9777eac81952971cfa97b783a7e71394
|