U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlo Caione" <ccaione@baylibre.com>
To: "Tom Rini" <trini@konsulko.com>, "Carlo Caione" <ccaione@baylibre.com>
Cc: GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
	u-boot@lists.u-boot-project.org,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
	"Ryder Lee" <ryder.lee@mediatek.com>,
	"Weijie Gao" <weijie.gao@mediatek.com>,
	"Chunfeng Yun" <chunfeng.yun@mediatek.com>,
	"Igor Belwon" <igor.belwon@mentallysanemainliners.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Julien Stephan" <jstephan@baylibre.com>,
	"Johan Jonker" <jbx6244@gmail.com>,
	"Macpaul Lin" <macpaul.lin@mediatek.com>,
	"Chris-QJ Chen" <chris-qj.chen@mediatek.com>,
	"Pablo Sun (孫毓翔)" <pablo.sun@mediatek.com>
Subject: Re: [PATCH 0/3] Add RITY devicetree preparation support
Date: Sat, 29 Aug 2026 15:59:07 +0200	[thread overview]
Message-ID: <DL1HC4XCVFUG.16T2OM80OX3BO@baylibre.com> (raw)
In-Reply-To: <20260828145911.GH3959812@bill-the-cat>

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 <ccaione@baylibre.com>
>> ---
>> 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	other threads:[~2026-08-29 13:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-28  8:39 [PATCH 0/3] Add RITY devicetree preparation support Carlo Caione
2026-08-28  8:39 ` [PATCH 1/3] arm: mediatek: add RITY devicetree preparation Carlo Caione
2026-08-28  8:39 ` [PATCH 2/3] arm: mediatek: add RITY devicetree compatibility commands Carlo Caione
2026-08-28  8:39 ` [PATCH 3/3] arm: mediatek: add bootembedded compatibility command Carlo Caione
2026-08-28 14:59 ` [PATCH 0/3] Add RITY devicetree preparation support Tom Rini
2026-08-29 13:59   ` Carlo Caione [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DL1HC4XCVFUG.16T2OM80OX3BO@baylibre.com \
    --to=ccaione@baylibre.com \
    --cc=GSS_MTK_Uboot_upstream@mediatek.com \
    --cc=chris-qj.chen@mediatek.com \
    --cc=chunfeng.yun@mediatek.com \
    --cc=dlechner@baylibre.com \
    --cc=igor.belwon@mentallysanemainliners.org \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jbx6244@gmail.com \
    --cc=jstephan@baylibre.com \
    --cc=macpaul.lin@mediatek.com \
    --cc=pablo.sun@mediatek.com \
    --cc=ryder.lee@mediatek.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=weijie.gao@mediatek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox