From: "Rafał Miłecki" <zajec5@gmail.com>
To: Vivek Unune <npcomplete13@gmail.com>
Cc: florian.fainelli@broadcom.com, Hauke Mehrtens <hauke@hauke-m.de>,
bcm-kernel-feedback-list@broadcom.com,
Rob Herring <robh+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ARM: dts: BCM5301X: Linksys EA9500 add fixed partitions
Date: Mon, 9 Nov 2020 18:28:38 +0100 [thread overview]
Message-ID: <b69adfa6-c867-816a-1f1d-d67fbfbd5f42@gmail.com> (raw)
In-Reply-To: <20201101200804.2460-1-npcomplete13@gmail.com>
On 01.11.2020 21:08, Vivek Unune wrote:
> This router has dual paritions to store trx firmware image and
> dual partitions for nvram. The second one in each of these cases acts
> as a backup store.
I'm quite sure CFE is supposed to flash new firmware to the backup
partition and then mark it as main one. The old firmware partition becomes a
new backup then.
That means you need to check which partition bootloader used to handle
partitioning properly.
> + partition@200000 {
> + label = "firmware";
> + reg = <0x0200000 0x01D00000>;
> + compatible = "brcm,trx";
> + };
> +
> + partition@1F00000 {
> + label = "failsafe";
> + reg = <0x01F00000 0x01D00000>;
> + read-only;
> + };
Here you assume CFE always boots from the first firmware partition.
Unless EA9500 CFE does sth stupid it seems like a 50% - 50% guess.
next prev parent reply other threads:[~2020-11-09 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 13:13 [PATCH] ARM: dts: BCM5301X: Linksys EA9500 add fixed partitions Vivek Unune
2020-10-26 13:30 ` Florian Fainelli
2020-10-26 15:39 ` Vivek Unune
2020-11-01 20:08 ` [PATCH v2] " Vivek Unune
2020-11-04 3:41 ` Florian Fainelli
2020-11-04 12:54 ` Vivek Unune
2020-11-09 17:28 ` Rafał Miłecki [this message]
2020-11-09 17:58 ` Vivek Unune
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=b69adfa6-c867-816a-1f1d-d67fbfbd5f42@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npcomplete13@gmail.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).