From: Rob Herring <robh@kernel.org>
To: Joel Peshkin <joel.peshkin@broadcom.com>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Srinivas Kandagatla" <srinivas.kandagatla@linaro.org>,
"Tom Rini" <trini@konsulko.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"Broadcom Kernel List" <bcm-kernel-feedback-list@broadcom.com>,
linux-kernel@vger.kernel.org, "Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH] dt-bindings: nvmem: u-boot, env: add Broadcom's variant binding
Date: Thu, 7 Apr 2022 13:17:03 -0500 [thread overview]
Message-ID: <Yk8qnxqXK7WZvXrS@robh.at.kernel.org> (raw)
In-Reply-To: <CAN3=V2vOVLc95ZYBUDo8J7ast4UQMnZm4uYmX63LpcJdZWnmNQ@mail.gmail.com>
On Thu, Apr 07, 2022 at 04:55:14AM -0700, Joel Peshkin wrote:
> Hi Rafal,
>
> The first 32b value is a magic number (endian swapped mnemonic of "uEnv"
> short for "u-boot environment"). Finding that magic number of a 4K
> boundary followed by a length and then a u-boot environment with a valid
> CRC permits a scan of the flash partition to locate the environment without
> knowing a-priori where it is.
So it doesn't need to be described in DT? But how does one identify
whether to scan the flash or not. You wouldn't want to do that one every
platform. IOW, it's a sufficient discovery mechanism for a custom build,
but not generic OS.
Rob
next prev parent reply other threads:[~2022-04-07 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 15:25 [PATCH] dt-bindings: nvmem: u-boot,env: add Broadcom's variant binding Rafał Miłecki
[not found] ` <CAN3=V2vOVLc95ZYBUDo8J7ast4UQMnZm4uYmX63LpcJdZWnmNQ@mail.gmail.com>
2022-04-07 18:17 ` Rob Herring [this message]
2022-09-21 11:57 ` [PATCH] dt-bindings: nvmem: u-boot, env: " Rafał Miłecki
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=Yk8qnxqXK7WZvXrS@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=joel.peshkin@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafal@milecki.pl \
--cc=srinivas.kandagatla@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=zajec5@gmail.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).