From: Anton Kachalov <gmouse@google.com>
To: unlisted-recipients:; (no To-header on input)
Cc: devicetree <devicetree@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ARM: dts: nuvoton: Fix flash layout
Date: Wed, 24 Mar 2021 08:12:05 +0100 [thread overview]
Message-ID: <CADVsX8_e9GNeceV-op5HwbxEnzUG_68izC11K=g46YWvCZE2Ag@mail.gmail.com> (raw)
In-Reply-To: <20210308171049.3962577-1-gmouse@google.com>
Gently ping
On Mon, 8 Mar 2021 at 18:11, <gmouse@google.com> wrote:
>
> From: "Anton D. Kachalov" <gmouse@google.com>
>
> This change follows OpenBMC partitions' naming layout.
>
> Signed-off-by: Anton D. Kachalov <gmouse@google.com>
> ---
> arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 38 +++++++----------------
> 1 file changed, 11 insertions(+), 27 deletions(-)
>
> diff --git a/arch/arm/boot/dts/nuvoton-npcm750-evb.dts b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> index 9f13d08f5804..55c5a89592d7 100644
> --- a/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> +++ b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> @@ -78,8 +78,8 @@ partitions@80000000 {
> compatible = "fixed-partitions";
> #address-cells = <1>;
> #size-cells = <1>;
> - bbuboot1@0 {
> - label = "bb-uboot-1";
> + u-boot@0 {
> + label = "u-boot";
> reg = <0x0000000 0x80000>;
> read-only;
> };
> @@ -88,38 +88,22 @@ bbuboot2@80000 {
> reg = <0x0080000 0x80000>;
> read-only;
> };
> - envparam@100000 {
> - label = "env-param";
> + u-boot-env@100000 {
> + label = "u-boot-env";
> reg = <0x0100000 0x40000>;
> read-only;
> };
> - spare@140000 {
> - label = "spare";
> - reg = <0x0140000 0xC0000>;
> - };
> kernel@200000 {
> label = "kernel";
> - reg = <0x0200000 0x400000>;
> - };
> - rootfs@600000 {
> - label = "rootfs";
> - reg = <0x0600000 0x700000>;
> - };
> - spare1@D00000 {
> - label = "spare1";
> - reg = <0x0D00000 0x200000>;
> - };
> - spare2@0F00000 {
> - label = "spare2";
> - reg = <0x0F00000 0x200000>;
> + reg = <0x0200000 0x580000>;
> };
> - spare3@1100000 {
> - label = "spare3";
> - reg = <0x1100000 0x200000>;
> + rofs@780000 {
> + label = "rofs";
> + reg = <0x0780000 0x1680000>;
> };
> - spare4@1300000 {
> - label = "spare4";
> - reg = <0x1300000 0x0>;
> + rwfs@1e00000 {
> + label = "rwfs";
> + reg = <0x1e00000 0x200000>;
> };
> };
> };
> --
> 2.30.1.766.gb4fecdf3b7-goog
>
next prev parent reply other threads:[~2021-03-24 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 17:10 [PATCH v2] ARM: dts: nuvoton: Fix flash layout gmouse
2021-03-24 7:12 ` Anton Kachalov [this message]
2021-03-31 8:03 ` Joel Stanley
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='CADVsX8_e9GNeceV-op5HwbxEnzUG_68izC11K=g46YWvCZE2Ag@mail.gmail.com' \
--to=gmouse@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).