From: Andrew Jeffery <andrew@aj.id.au>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v2 1/2] ARM: dts: Add Facebook BMC flash layout
Date: Thu, 08 Nov 2018 12:15:56 +1030 [thread overview]
Message-ID: <1541641556.1495362.1569509568.7BE039CA@webmail.messagingengine.com> (raw)
In-Reply-To: <c5e56fc4-397f-a38b-6378-99eecce1180b@fb.com>
On Thu, 8 Nov 2018, at 10:48, Tao Ren wrote:
> On 11/7/18 4:02 PM, Andrew Jeffery wrote:
> >> +partitions {
> >> + compatible = "fixed-partitions";
> >> + #address-cells = <1>;
> >> + #size-cells = <1>;
> >> +
> >> + u-boot at 0 {
> >> + reg = <0x0 0x60000>;
> >> + label = "u-boot";
> >> + };
> >> +
> >> + u-boot-env at 60000 {
> >> + reg = <0x60000 0x20000>;
> >> + label = "env";
> >> + };
> >> +
> >> + fit at 80000 {
> >> + reg = <0x80000 0x1b80000>;
> >> + label = "fit";
> >> + };
> >> +
> >> + data0 at 1c00000 {
> >> + reg = <0x1c00000 0x400000>;
> >> + label = "data0";
> >> + };
> >> +
> >> + flash0 at 0 {
> >> + reg = <0x0 0x2000000>;
> >> + label = "flash0";
> >> + };
> >
> > Is this necessary? Isn't the same thing achieved with the /dev/mtd0 device?
>
> Hi Andrew,
>
> Thank you for the review! The new layout file is needed mainly because
> of "data0" partition: several facebook platforms use the partition as
> "persistent" storage.
>
> As for "flash0", technically it's not needed (as you pointed out, /dev/
> mtd0 covers the entire flash if master_partition is enabled). It's still
> here to avoid breaking some legacy applications.
This is what I expected. I think it might be worth adding a comment, given
you are respinning the series to address my comments on the board
devicetree patch.
Anyway, thanks for the clarification.
Andrew
next prev parent reply other threads:[~2018-11-08 1:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 4:28 [PATCH v2 1/2] ARM: dts: Add Facebook BMC flash layout Tao Ren
2018-11-08 0:02 ` Andrew Jeffery
2018-11-08 0:18 ` Tao Ren
2018-11-08 1:45 ` Andrew Jeffery [this message]
2018-11-08 2:31 ` Tao Ren
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=1541641556.1495362.1569509568.7BE039CA@webmail.messagingengine.com \
--to=andrew@aj.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
/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