On Fri Aug 28, 2026 at 4:59 PM CEST, Tom Rini wrote:
> On Fri, Aug 28, 2026 at 10:39:55AM +0200, Carlo Caione wrote:
>> RITY images select a base devicetree and an ordered list of overlays
>> through the storage, storage_dev, dtb_path, boot_dtb, fdtfile and list_dtbo
>> environment variables. EFI boot needs the selected tree to be assembled
>> and published through fdt_addr before the operating system is started.
>> 
>> Add MediaTek support to consume that interface. It locates the selected
>> source on GPT block partitions or on the RITY UBI/UBIFS NOR layout, loads
>> the base DTB, applies list_dtbo in order and publishes the completed tree.
>> Both raw and authenticated DTB and DTBO inputs are supported.
>> 
>> Expose mtk_fdt_prepare for interactive use. Retain the dtbprobe and
>> fdtprobe command names and positional arguments used by RITY EFI boot
>> environments. Also provide bootembedded for legacy boot. It locates and
>> runs the appended RITY boot script through the standard source command,
>> leaving the legacy policy and authentication to source and bootm.
>> 
>> The implementation uses existing block, MTD, UBI/UBIFS, libfdt overlay,
>> image verification, source and bootm services.
>> 
>> Signed-off-by: Carlo Caione <[email protected]>
>> ---
>> Carlo Caione (3):
>>       arm: mediatek: add RITY devicetree preparation
>>       arm: mediatek: add RITY devicetree compatibility commands
>>       arm: mediatek: add bootembedded compatibility command
>> 
>>  arch/arm/mach-mediatek/Kconfig            |  45 +++
>>  arch/arm/mach-mediatek/Makefile           |   3 +
>>  arch/arm/mach-mediatek/cmd_bootembedded.c |  59 ++++
>>  arch/arm/mach-mediatek/cmd_fdt_prepare.c  |  66 ++++
>>  arch/arm/mach-mediatek/fdt_prepare.c      | 502 
>> ++++++++++++++++++++++++++++++
>>  arch/arm/mach-mediatek/fdt_prepare.h      |  10 +
>
> Is this some mediatek specific format? But even if so, cmds should go
> under something like cmd/mediatek (and get docs..).

Yes, this is Mediatek-specific. I’ll move the commands under
cmd/mediatek (didn't notice that) and add documentation in v2.

Cheers,

--
Carlo Caione

Reply via email to