From: David Lechner via U-Boot <u-boot@lists.u-boot-project.org>
To: Carlo Caione <ccaione@baylibre.com>,
GSS_MTK_Uboot_upstream <GSS_MTK_Uboot_upstream@mediatek.com>,
u-boot@lists.denx.de
Cc: Ryder Lee <ryder.lee@mediatek.com>,
Weijie Gao <weijie.gao@mediatek.com>,
Chunfeng Yun <chunfeng.yun@mediatek.com>,
Igor Belwon <igor.belwon@mentallysanemainliners.org>,
Julien Stephan <jstephan@baylibre.com>,
Macpaul Lin <Macpaul.Lin@mediatek.com>,
Tom Rini <trini@konsulko.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Julien Masson <jmasson@baylibre.com>,
Johan Jonker <jbx6244@gmail.com>,
Quentin Schulz <u-boot@0leil.net>,
Marek Vasut <marek.vasut+renesas@mailbox.org>,
Vitor Sato Eschholz <vsatoes@baylibre.com>
Subject: Re: [PATCH 4/4] doc: board: mediatek: document Genio 700 SPL boot
Date: Tue, 21 Jul 2026 09:50:25 -0500 [thread overview]
Message-ID: <2ca02789-5806-4672-99fd-30ea217fe5f5@baylibre.com> (raw)
In-Reply-To: <DK47KU0R1WUG.1SFYMAO1PAA7B@baylibre.com>
On 7/21/26 6:22 AM, Carlo Caione wrote:
> On Tue Jul 21, 2026 at 2:38 AM CEST, David Lechner wrote:
>> On 7/18/26 11:16 AM, Carlo Caione wrote:
>
...
>>> +``ddr-loader.bin``
>>> + The MediaTek DDR loader for the board. The input may be shorter than
>>> + ``0x4b000`` bytes; binman pads it with zeroes to the offset reserved before
>>> + SPL. It must have been built with ``SPL_OFFSET=0x4b000``,
>>
>> Inconsistent formatting. Should be ...
>>
>> ``SPL``
>> It must ...
>>
>> ?
>
> I don't think I follow. The phrase is '... before SPL', SPL is not an
> external binary file, it should not be on its own line.
Sorry, the `` above threw me off, I thought for a minute that this was
starting a new section. Ignore that comment.
>
>>> + ``SPL_SIZE=CONFIG_SPL_MAX_SIZE`` and an SPL destination and entry address
>>> + matching ``CONFIG_SPL_TEXT_BASE``.
>>> +
>>> +``BL31``
>>
>> Why is this BL31 instead of TF-A?
>
> Because BL31 is compiled (it is) TF-A, they are basically the same
> thing. Is this a nomenclature problem?
I would either expect that the names (TF-A, OP-TEE, U-Boot) to be used
everywhere or BL31, BL32, BL33 to be used everywhere, not a mix of both.
However, I see now that these are existing variable names in binman.
So obviously can't change them.
>
>>> + The path to the TF-A BL31 binary built for MT8188/MT8390. It is loaded and
>>> + entered at ``0x54601000``.
>>> +
>>> +``TEE``
>>> + The path to the OP-TEE binary. A standard OP-TEE v1 ``tee.bin`` image is
>>> + supported. The FIT loads it at ``0x431fffe4`` and enters it at
>>> + ``0x43200000``.
>>> +
...
>
>>> +Using Genio Tools
>>> +~~~~~~~~~~~~~~~~~
>>
>> Probably deserves an external link on where to get genio-tools and pre-build
>> images.
>
> I'll add a link for the genio-tools. About the pre-build images there is
> no place the user can download them from (for now), they are currently
> compiled as part of the yocto image / distro.
>
I was thinking of https://genio.mediatek.com/doc/iot-yocto/latest/sw/yocto/download.html
next prev parent reply other threads:[~2026-07-21 14:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 16:16 [PATCH 0/4] arm: mediatek: add Genio 700 SPL boot support Carlo Caione
2026-07-18 16:16 ` [PATCH 1/4] arm: dts: mediatek: prepare Genio 700 devices for SPL Carlo Caione
2026-07-21 0:01 ` David Lechner via U-Boot
2026-07-21 8:35 ` Carlo Caione via U-Boot
2026-07-22 21:01 ` David Lechner via U-Boot
2026-07-18 16:16 ` [PATCH 2/4] configs: mt8390: enable eMMC FIT boot from SPL Carlo Caione
2026-07-21 0:05 ` David Lechner via U-Boot
2026-07-18 16:16 ` [PATCH 3/4] arm: mediatek: mt8390: build boot images with binman Carlo Caione
2026-07-18 16:16 ` [PATCH 4/4] doc: board: mediatek: document Genio 700 SPL boot Carlo Caione
2026-07-21 0:38 ` David Lechner via U-Boot
2026-07-21 11:22 ` Carlo Caione via U-Boot
2026-07-21 14:50 ` David Lechner via U-Boot [this message]
2026-07-21 16:00 ` Carlo Caione via U-Boot
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=2ca02789-5806-4672-99fd-30ea217fe5f5@baylibre.com \
--to=u-boot@lists.u-boot-project.org \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=Macpaul.Lin@mediatek.com \
--cc=ccaione@baylibre.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=jmasson@baylibre.com \
--cc=jstephan@baylibre.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=ryder.lee@mediatek.com \
--cc=trini@konsulko.com \
--cc=u-boot@0leil.net \
--cc=u-boot@lists.denx.de \
--cc=vsatoes@baylibre.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.