From: John Wang <wangzhiqiang.bj@bytedance.com>
To: yulei.sh@bytedance.com, xuxiaohan@bytedance.com,
openbmc@lists.ozlabs.org, joel@jms.id.au
Subject: [PATCH linux dev-5.8 v3 1/2] ARM: dts: Add 64MiB OpenBMC flash layout
Date: Tue, 29 Sep 2020 14:39:54 +0800 [thread overview]
Message-ID: <20200929063955.1206-1-wangzhiqiang.bj@bytedance.com> (raw)
This is an alternate layout used by OpenBMC systems
The division of space is as follows:
u-boot + env: 0.5MB
kernel/FIT: 5MB
rofs: 42.5MB
rwfs: 16MB
Signed-off-by: John Wang <wangzhiqiang.bj@bytedance.com>
---
v2:
- Add copyright notice
v3:
- nothing
---
.../arm/boot/dts/openbmc-flash-layout-64.dtsi | 35 +++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
diff --git a/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi b/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
new file mode 100644
index 000000000000..c8e0409d889e
--- /dev/null
+++ b/arch/arm/boot/dts/openbmc-flash-layout-64.dtsi
@@ -0,0 +1,35 @@
+// SPDX-License-Identifier: GPL-2.0+
+/*
+ * Copyright (C) 2020 Bytedance.
+ */
+
+partitions {
+ compatible = "fixed-partitions";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ u-boot@0 {
+ reg = <0x0 0x60000>; // 384KB
+ label = "u-boot";
+ };
+
+ u-boot-env@e0000 {
+ reg = <0x60000 0x20000>; // 128KB
+ label = "u-boot-env";
+ };
+
+ kernel@100000 {
+ reg = <0x80000 0x500000>; // 5MB
+ label = "kernel";
+ };
+
+ rofs@a00000 {
+ reg = <0x580000 0x2a80000>; // 42.5MB
+ label = "rofs";
+ };
+
+ rwfs@6000000 {
+ reg = <0x3000000 0x1000000>; // 16MB
+ label = "rwfs";
+ };
+};
--
2.25.1
next reply other threads:[~2020-09-29 6:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 6:39 John Wang [this message]
2020-09-29 6:39 ` [PATCH linux dev-5.8 v3 2/2] ARM: dts: aspeed: Add Bytedance g220a BMC machine John Wang
2020-10-07 6:38 ` Joel Stanley
2020-10-07 6:53 ` 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=20200929063955.1206-1-wangzhiqiang.bj@bytedance.com \
--to=wangzhiqiang.bj@bytedance.com \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=xuxiaohan@bytedance.com \
--cc=yulei.sh@bytedance.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).