[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACPK8XdgLP7XSH0Zkej87ynnKTbEUW+RUBiSMgDH1H-LD5VXhg@mail.gmail.com>
Date: Thu, 3 Jun 2021 06:02:07 +0000
From: Joel Stanley <joel@....id.au>
To: Lei Yu <yulei.sh@...edance.com>,
Quan Nguyen <quan@...amperecomputing.com>
Cc: Troy Lee <troy_lee@...eedtech.com>,
John Wang <wangzhiqiang.bj@...edance.com>,
Rob Herring <robh+dt@...nel.org>,
Andrew Jeffery <andrew@...id.au>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-arm-kernel@...ts.infradead.org>,
"moderated list:ARM/ASPEED MACHINE SUPPORT"
<linux-aspeed@...ts.ozlabs.org>,
open list <linux-kernel@...r.kernel.org>, leetroy@...il.com
Subject: Re: [External] Re: [PATCH v1] ARM: dts: Fix 64MiB OpenBMC flash
layout and aspeed-ast2600-evb.dts
On Fri, 16 Apr 2021 at 07:35, Lei Yu <yulei.sh@...edance.com> wrote:
>
> On Fri, Apr 16, 2021 at 11:03 AM Joel Stanley <joel@....id.au> wrote:
> >
> > On Tue, 16 Mar 2021 at 08:59, Troy Lee <troy_lee@...eedtech.com> wrote:
> > >
> > > Aspeed AST2600 u-boot requires 600KiB+ flash space. Sharing the same
> > > openbmc-flash-layout-64.dtsi requires to resize the flash partition.
> > >
> > > The updated flash layout as follows:
> > > - u-boot: 896 KiB
> > > - u-boot-env: 128 KiB
> > > - kernel: 9MiB
> > > - rofs: 32 MiB
> > > - rwfs: 22 MiB
> >
> > Changing the 64MB layout will break the systems that are already using
> > this layout. I'll get the Bytedance people to chime in, as theirs is
> > the only system using this layout so far.
> >
> > John, Lei?
>
> Because the kernel's offset is updated, several other changes are required:
> 1. The related offsets, which is already sent to
> https://gerrit.openbmc-project.xyz/c/openbmc/meta-phosphor/+/39343
> 2. The u-boot patch to update the `bootm` address and make sure it
> only applies to the 64MiB layout.
>
> Without the above two changes, I would suggest holding the merge.
Reviewed-by: Joel Stanley <joel@....id.au>
Just confirming that we are okay to go ahead with this change, as per
the discussion on the openbmc list[1].
[1] https://lore.kernel.org/openbmc/CACPK8XdVNXSfzDBPryjQh_4S0yU4Tp6VOOtju+L_DcfgHumPJw@mail.gmail.com/
Cheers,
Joel
Powered by blists - more mailing lists