All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomer Maimon <tmaimon77@gmail.com>
To: Benjamin Fair <benjaminfair@google.com>
Cc: devicetree <devicetree@vger.kernel.org>,
	Avi Fishman <avifishman70@gmail.com>,
	Patrick Venture <venture@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Anton Kachalov <gmouse@google.com>,
	Tali Perry <tali.perry1@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: dts: nuvoton: Fix flash layout
Date: Sun, 21 Feb 2021 18:53:41 +0200	[thread overview]
Message-ID: <CAP6Zq1jf4-XAhLQxqNx3LM7-YzDr8zaVPb-jznn8o=frxTotdQ@mail.gmail.com> (raw)
In-Reply-To: <CADKL2t6P4gaSUZEFgk7y+TNBRw0Lhf8mXTxzLdbe3FhGs0WH+w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3374 bytes --]

Hi Benjamin and Anton,

Sorry for the late reply,

The EVB FIU0-CS0 partitioning is used for testing the EVB and this is why
it is different than the OpenBMC flash layout.



Are you using the NPCM7XX EVB for OpenBMC? if yes we can consider to modify
the flash partition to OpenBMC use.

On Thu, 18 Feb 2021 at 19:11, Benjamin Fair <benjaminfair@google.com> wrote:

> On Thu, 18 Feb 2021 at 04:42, <gmouse@google.com> wrote:
> >
> > From: "Anton D. Kachalov" <gmouse@google.com>
> >
> > This change satisfy OpenBMC requirements for flash layout.
> >
> > Signed-off-by: Anton D. Kachalov <gmouse@google.com>
> > ---
> >  arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 28 +++++++----------------
> >  1 file changed, 8 insertions(+), 20 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> > index bd1eb6ee380f..741c1fee8552 100644
> > --- a/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> > +++ b/arch/arm/boot/dts/nuvoton-npcm750-evb.dts
> > @@ -182,8 +182,8 @@ bbuboot2@80000 {
> >                                 reg = <0x0080000 0x80000>;
> >                                 read-only;
> >                                 };
> > -                       envparam@100000 {
> > -                               label = "env-param";
> > +                       ubootenv@100000 {
> > +                               label = "u-boot-env";
> >                                 reg = <0x0100000 0x40000>;
> >                                 read-only;
> >                                 };
> > @@ -195,25 +195,13 @@ kernel@200000 {
> >                                 label = "kernel";
> >                                 reg = <0x0200000 0x400000>;
> >                                 };
> > -                       rootfs@600000 {
> > -                               label = "rootfs";
> > -                               reg = <0x0600000 0x700000>;
> > +                       rofs@780000 {
> > +                               label = "rofs";
> > +                               reg = <0x0780000 0x1680000>;
> >                                 };
> > -                       spare1@D00000 {
> > -                               label = "spare1";
> > -                               reg = <0x0D00000 0x200000>;
> > -                               };
> > -                       spare2@0F00000 {
> > -                               label = "spare2";
> > -                               reg = <0x0F00000 0x200000>;
> > -                               };
> > -                       spare3@1100000 {
> > -                               label = "spare3";
> > -                               reg = <0x1100000 0x200000>;
> > -                               };
> > -                       spare4@1300000 {
> > -                               label = "spare4";
> > -                               reg = <0x1300000 0x0>;
> > +                       rwfs@1e00000 {
> > +                               label = "rwfs";
> > +                               reg = <0x1e00000 0x200000>;
> >                         };
>
> I recommend just including the openbmc-flash-layout.dtsi file here
> instead since that contains the common flash layout for most OpenBMC
> systems.
>
> Good solution,
Do you mean nuvoton-openbmc-flash-layout?

> >                 };
> >         };
> > --
> > 2.30.0.478.g8a0d178c01-goog
> >
>

Thanks,

Tomer

[-- Attachment #2: Type: text/html, Size: 5642 bytes --]

  reply	other threads:[~2021-02-21 16:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 12:25 [PATCH] ARM: dts: nuvoton: Fix flash layout gmouse
2021-02-18 12:25 ` gmouse
2021-02-18 12:47 ` Paul Menzel
2021-02-18 17:10 ` Benjamin Fair
2021-02-18 17:10   ` Benjamin Fair
2021-02-21 16:53   ` Tomer Maimon [this message]
2021-02-22  9:26     ` Anton Kachalov
2021-02-22  9:26       ` Anton Kachalov
2021-02-22 10:21       ` Avi Fishman
2021-02-22 10:21         ` Avi Fishman
2021-02-22 14:10         ` IS20 Ofer Eilon
2021-02-22 14:10           ` IS20 Ofer Eilon
2021-02-22 14:24           ` Anton Kachalov
2021-02-22 14:24             ` Anton Kachalov
2021-02-23 13:14             ` Avi Fishman
2021-02-23 13:14               ` Avi Fishman
2021-02-26 20:10     ` Anton Kachalov
2021-03-01 13:36       ` Tomer Maimon
  -- strict thread matches above, loose matches on Subject: below --
2021-02-07 17:58 Anton Kachalov
2021-02-07 22:28 ` Anton Kachalov
2021-02-09  0:08   ` Joel Stanley
2021-02-08 12:50 ` Anton Kachalov

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='CAP6Zq1jf4-XAhLQxqNx3LM7-YzDr8zaVPb-jznn8o=frxTotdQ@mail.gmail.com' \
    --to=tmaimon77@gmail.com \
    --cc=avifishman70@gmail.com \
    --cc=benjaminfair@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gmouse@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=tali.perry1@gmail.com \
    --cc=venture@google.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.