ZBI_TYPE_DRV_BOARD_INFO payload.
for ZBI_KERNEL_DRIVER_AMLOGIC_HDCP
for ZBI_KERNEL_DRIVER_AMLOGIC_RNG_V1
for ZBI_KERNEL_DRIVER_AMLOGIC_RNG_V2
for ZBI_KERNEL_DRIVER_ARM_GENERIC_TIMER
for ZBI_KERNEL_DRIVER_ARM_GIC_V2
for ZBI_KERNEL_DRIVER_ARM_GIC_V3
for ZBI_KERNEL_DRIVER_ARM_PSCI
Definitions of actions which may be taken by a generic 32 bit watchdog timer
kernel driver which may be passed by a bootloader. Field definitions are as
follows.
Defines a register write action for a generic kernel watchdog driver. An
action consists of the following steps.
for ZBI_KERNEL_DRIVER_RISCV_GENERIC_TIMER
for ZBI_KERNEL_DRIVER_RISCV_PLIC
Kernel driver struct that can be used for simple drivers.
Used by ZBI_KERNEL_DRIVER_PL011_UART, ZBI_KERNEL_DRIVER_AMLOGIC_UART, and
ZBI_KERNEL_DRIVER_GENI_UART, ZBI_KERNEL_DRIVER_I8250_MMIO_UART.
Used by ZBI_KERNEL_DRIVER_I8250_PIO_UART.
Flags associated with an item. A valid flags value must always include
ZBI_FLAGS_VERSION. Values should also contain ZBI_FLAGS_CRC32 for any item
where it’s feasible to compute the CRC32 at build time. Other flags are
specific to each type.
Each header must be 8-byte aligned. The length field specifies the
actual payload length and does not include the size of padding.
The kernel image. In a bootable ZBI this item must always be first,
immediately after the ZBI_TYPE_CONTAINER header. The contiguous memory
image of the kernel is formed from the ZBI_TYPE_CONTAINER header, the
ZBI_TYPE_KERNEL_{ARCH} header, and the payload.
The ZBI_TYPE_MEM_CONFIG payload consist of one or more zbi_mem_range_t
entries.
ZBI_TYPE_NVRAM payload.
ZBI_TYPE_DRV_PARTITION_MAP payload. This header is immediately followed by
an array of the corresponding zbi_partition_t.
ZBI_TYPE_PLATFORM_ID payload.
ZBI_TYPE_FRAMEBUFFER payload.
The ZBI_TYPE_CPU_TOPOLOGY payload consists of an array of
zbi_topology_node_t, giving a flattened tree-like description of the CPU
configuration according to the entity hierarchy.