openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tomer Maimon <tmaimon77@gmail.com>
To: Anton Kachalov <gmouse@google.com>
Cc: devicetree <devicetree@vger.kernel.org>,
	Benjamin Fair <benjaminfair@google.com>,
	Avi Fishman <avifishman70@gmail.com>,
	Patrick Venture <venture@google.com>,
	OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Tali Perry <tali.perry1@gmail.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] ARM: dts: nuvoton: Fix flash layout
Date: Mon, 1 Mar 2021 15:36:58 +0200	[thread overview]
Message-ID: <CAP6Zq1hd56Su6YjqyOJP2fDHuYYkShEGsFaYou6fGzhZhu-HKQ@mail.gmail.com> (raw)
In-Reply-To: <CADVsX8-4gJYs1P7y4VazyXPNC2TxgmUi1MgOpLgx3iAV9n62Hg@mail.gmail.com>

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

Hi Anton,

The reason the u-boot Env is at 0x100000 address is that some
costumers have:
one copy of Bootblock and U-boot at 0x0 - 0x80000
second copy of Bootblock and U-boot at 0x80000 - 0x100000.

we have two options;
1. Modify the OpenBMC device tree flash layout u-boot Env address to
0x100000.
2. Add a patch to OpnBMC platform that using openbmc flash layout to
modify CONFIG_ENV_OFFSET
in the u-boot.

Thanks,

Tomer


On Fri, 26 Feb 2021 at 22:10, Anton Kachalov <gmouse@google.com> wrote:

> Hello, Tomer.
>
> Seems like Nuvoton's u-boot expects the uboot-env at different address
> comparing to openbmc-flash-layout.dtsi:
>
>
> https://github.com/Nuvoton-Israel/u-boot/blob/npcm7xx-v2019.01/include/configs/poleg.h#L30
>
> Vs.
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/openbmc-flash-layout.dtsi#n13
>
> The change is more about making partitions naming the same as expected by
> OpenBMC.
>
> On Sun, 21 Feb 2021 at 17:40, Tomer Maimon <tmaimon77@gmail.com> wrote:
>
>> 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: 8751 bytes --]

  reply	other threads:[~2021-03-01 13:24 UTC|newest]

Thread overview: 15+ 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:47 ` Paul Menzel
2021-02-18 17:10 ` Benjamin Fair
2021-02-21 16:53   ` Tomer Maimon
2021-02-22  9:26     ` Anton Kachalov
2021-02-22 10:21       ` Avi Fishman
2021-02-22 14:10         ` IS20 Ofer Eilon
2021-02-22 14:24           ` Anton Kachalov
2021-02-23 13:14             ` Avi Fishman
2021-02-26 20:10     ` Anton Kachalov
2021-03-01 13:36       ` Tomer Maimon [this message]
  -- 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=CAP6Zq1hd56Su6YjqyOJP2fDHuYYkShEGsFaYou6fGzhZhu-HKQ@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 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).