From: Andrew Davis <afd@ti.com>
To: Nathan Morrisson <nmorrisson@phytec.com>, <nm@ti.com>,
<vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<upstream@lists.phytec.de>, <w.egorov@phytec.de>
Subject: Re: [PATCH 0/2] *** Add fixed-paritions to phyCORE-AM62x and phyCORE-AM64x ***
Date: Fri, 15 Dec 2023 13:20:48 -0600 [thread overview]
Message-ID: <9f86870c-88cc-43ea-800c-3a05482953aa@ti.com> (raw)
In-Reply-To: <20231215191838.1925082-1-nmorrisson@phytec.com>
On 12/15/23 1:18 PM, Nathan Morrisson wrote:
> Add a fixed-partitions node to the NOR flash of the phyCORE-AM62x
> and phyCORE-AM64x to enable the bootloader to fixup the partitions
> during boot.
>
Why can't your bootloader add these nodes?
Andrew
> Nathan Morrisson (2):
> arm64: dts: ti: k3-am62-phycore-som: Add fixed-partitions to NOR Flash
> arm64: dts: ti: k3-am64-phycore-som: Add fixed-partitions to NOR Flash
>
> arch/arm64/boot/dts/ti/k3-am62-phycore-som.dtsi | 6 ++++++
> arch/arm64/boot/dts/ti/k3-am64-phycore-som.dtsi | 6 ++++++
> 2 files changed, 12 insertions(+)
>
next prev parent reply other threads:[~2023-12-15 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 19:18 [PATCH 0/2] *** Add fixed-paritions to phyCORE-AM62x and phyCORE-AM64x *** Nathan Morrisson
2023-12-15 19:18 ` [PATCH 1/2] arm64: dts: ti: k3-am62-phycore-som: Add fixed-partitions to NOR Flash Nathan Morrisson
2023-12-15 19:18 ` [PATCH 2/2] arm64: dts: ti: k3-am64-phycore-som: " Nathan Morrisson
2023-12-15 19:20 ` Andrew Davis [this message]
2023-12-18 18:47 ` [PATCH 0/2] *** Add fixed-paritions to phyCORE-AM62x and phyCORE-AM64x *** Nathan Morrisson
2023-12-18 19:41 ` Andrew Davis
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=9f86870c-88cc-43ea-800c-3a05482953aa@ti.com \
--to=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nmorrisson@phytec.com \
--cc=robh+dt@kernel.org \
--cc=upstream@lists.phytec.de \
--cc=vigneshr@ti.com \
--cc=w.egorov@phytec.de \
/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