From: Tao Ren <rentao.bupt@gmail.com>
To: Andrew Jeffery <andrew@codeconstruct.com.au>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Tao Ren <taoren@meta.com>
Subject: Re: [PATCH 1/5] ARM: dts: aspeed: Expand data0 partition in facebook-bmc-flash-layout-128.dtsi
Date: Thu, 3 Jul 2025 21:45:44 -0700 [thread overview]
Message-ID: <aGdceHVCEaWxo5QG@localhost.localdomain> (raw)
In-Reply-To: <78f9fcbc58261064f248e95eb7740549e338bc78.camel@codeconstruct.com.au>
On Fri, Jul 04, 2025 at 09:36:29AM +0930, Andrew Jeffery wrote:
> On Tue, 2025-07-01 at 22:04 -0700, rentao.bupt@gmail.com wrote:
> > From: Tao Ren <rentao.bupt@gmail.com>
> >
> > Expand data0 partition to 64MB in facebook-bmc-flash-layout-128.dtsi for
> > larger persistent storage.
> >
> > Signed-off-by: Tao Ren <rentao.bupt@gmail.com>
> > ---
> > .../boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
> >
> > diff --git a/arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi b/arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi
> > index 7f3652dea550..efd92232cda2 100644
> > --- a/arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi
> > +++ b/arch/arm/boot/dts/aspeed/facebook-bmc-flash-layout-128.dtsi
> > @@ -32,19 +32,19 @@ image-meta@f0000 {
> > };
> >
> > /*
> > - * FIT image: 119 MB.
> > + * FIT image: 63 MB.
> > */
> > fit@100000 {
> > - reg = <0x100000 0x7700000>;
> > + reg = <0x100000 0x3f00000>;
> > label = "fit";
> > };
> >
> > /*
> > - * "data0" partition (8MB) is used by Facebook BMC platforms as
> > + * "data0" partition (64MB) is used by Facebook BMC platforms as
> > * persistent data store.
> > */
> > - data0@7800000 {
> > - reg = <0x7800000 0x800000>;
> > + data0@4000000 {
> > + reg = <0x4000000 0x4000000>;
> > label = "data0";
> > };
> >
>
> Two existing systems use this dtsi:
>
> > git grep facebook-bmc-flash-layout-128.dtsi
> arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts:#include "facebook-bmc-flash-layout-128.dtsi"
> arch/arm/boot/dts/aspeed/ast2600-facebook-netbmc-common.dtsi:#include "facebook-bmc-flash-layout-128.dtsi"
>
> This change requires a full reflash of those devices, which is pretty
> disruptive.
>
> It seems more appropriate to me to create a separate dtsi for the new
> flash layout to use in new systems.
>
> Andrew
Hi Andrew,
I agree it's better to create a new layout, and I will take care of it
in v2. The migration is already done for all the network BMC platforms
except elbert/darwin, and having separate layouts will make my life
easier :)
Any suggestions about the file name of the new layout?
Thanks,
Tao
next prev parent reply other threads:[~2025-07-04 4:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 5:04 [PATCH 0/5] ARM: dts: aspeed: Add Meta Darwin dts rentao.bupt
2025-07-02 5:04 ` [PATCH 1/5] ARM: dts: aspeed: Expand data0 partition in facebook-bmc-flash-layout-128.dtsi rentao.bupt
2025-07-04 0:06 ` Andrew Jeffery
2025-07-04 4:45 ` Tao Ren [this message]
2025-07-02 5:04 ` [PATCH 2/5] ARM: dts: aspeed: Remove eMMC from ast2600-facebook-netbmc-common.dtsi rentao.bupt
2025-07-04 0:08 ` Andrew Jeffery
2025-07-04 4:46 ` Tao Ren
2025-07-02 5:04 ` [PATCH 3/5] ARM: dts: aspeed: elbert: Enable eMMC device rentao.bupt
2025-07-02 5:04 ` [PATCH 4/5] ARM: dts: aspeed: fuji: " rentao.bupt
2025-07-02 5:04 ` [PATCH 5/5] ARM: dts: aspeed: Add Facebook Darwin (AST2600) BMC rentao.bupt
2025-07-02 7:40 ` Andrew Lunn
2025-07-02 23:09 ` Tao Ren
2025-07-03 7:58 ` Andrew Lunn
2025-07-03 22:15 ` Tao Ren
2025-07-04 7:37 ` Andrew Lunn
2025-07-06 4:12 ` Tao Ren
2025-07-02 7:50 ` Krzysztof Kozlowski
2025-07-02 23:13 ` Tao Ren
2025-07-02 15:04 ` [PATCH 0/5] ARM: dts: aspeed: Add Meta Darwin dts Rob Herring (Arm)
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=aGdceHVCEaWxo5QG@localhost.localdomain \
--to=rentao.bupt@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=taoren@meta.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.