From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Frank Wunderlich <linux@fw-web.de>, linux-mediatek@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] arm64: dts: use size of reserved partition for bl2
Date: Mon, 3 Apr 2023 14:43:37 +0200 [thread overview]
Message-ID: <601a8435-8e2a-2c25-5fe3-40be62269469@collabora.com> (raw)
In-Reply-To: <20230403105818.29624-1-linux@fw-web.de>
Il 03/04/23 12:58, Frank Wunderlich ha scritto:
> From: Frank Wunderlich <frank-w@public-files.de>
>
> To store uncompressed bl2 more space is required than partition is
> actually defined.
>
> Signed-off-by: Frank Wunderlich <frank-w@public-files.de>
If this doesn't get changed anymore, I'm fine with it... but a question arises:
did you send patches to add your BPI-r3 board(s) to upstream u-boot?
> ---
> I used the definition i got from mtk used in their SDK uboot.
>
> Openwrt uses also the first reserved partition to give bl2 more
> space:
>
> https://git.openwrt.org/?p=openwrt/openwrt.git;a=blob;f=target/linux/mediatek/dts/mt7986a-bananapi-bpi-r3-nor.dts;h=f597b869abc80d1a73f44ebb85ad4da17376bb52;hb=HEAD#l22
>
> so imho it should be same in mainline to not require complex bl2
> compression.
Regards,
Angelo
next prev parent reply other threads:[~2023-04-03 12:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 10:58 Frank Wunderlich
2023-04-03 12:43 ` AngeloGioacchino Del Regno [this message]
2023-04-03 13:56 ` Aw: " Frank Wunderlich
2023-04-03 14:04 ` AngeloGioacchino Del Regno
2023-04-03 14:54 ` Aw: " Frank Wunderlich
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=601a8435-8e2a-2c25-5fe3-40be62269469@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=frank-w@public-files.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@fw-web.de \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
/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
all inboxes | Powered by JetHome®