u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: "Paweł Anikiel" <pan@semihalf.com>
To: u-boot@lists.denx.de, marex@denx.de,
	simon.k.r.goldschmidt@gmail.com, tien.fong.chee@intel.com
Cc: sjg@chromium.org, ka@semihalf.com, mw@semihalf.com,
	amstan@chromium.org, "Paweł Anikiel" <pan@semihalf.com>
Subject: [PATCH 3/4] arm: dts: chameleonv3: Override chameleonv3 bitstream names
Date: Fri, 26 Aug 2022 09:53:16 +0200	[thread overview]
Message-ID: <20220826075317.1888714-4-pan@semihalf.com> (raw)
In-Reply-To: <20220826075317.1888714-1-pan@semihalf.com>

Set the bitstream name per Chameleon variant. This allows the same
boot filesystem with all bitstream variants to be used on different
boards.

Signed-off-by: Paweł Anikiel <pan@semihalf.com>
---
 arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi | 4 ++++
 arch/arm/dts/socfpga_arria10_chameleonv3_480_2-u-boot.dtsi | 4 ++++
 2 files changed, 8 insertions(+)

diff --git a/arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi b/arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi
index e789d49657..a7aa17b220 100644
--- a/arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi
+++ b/arch/arm/dts/socfpga_arria10_chameleonv3_270_3-u-boot.dtsi
@@ -6,3 +6,7 @@
 #include "socfpga_arria10-handoff.dtsi"
 #include "socfpga_arria10_handoff_u-boot.dtsi"
 #include "socfpga_arria10_mercury_aa1-u-boot.dtsi"
+
+&fpga_mgr {
+	altr,bitstream = "fpga-270-3.itb";
+};
diff --git a/arch/arm/dts/socfpga_arria10_chameleonv3_480_2-u-boot.dtsi b/arch/arm/dts/socfpga_arria10_chameleonv3_480_2-u-boot.dtsi
index 7bbcc471c5..82a94894ea 100644
--- a/arch/arm/dts/socfpga_arria10_chameleonv3_480_2-u-boot.dtsi
+++ b/arch/arm/dts/socfpga_arria10_chameleonv3_480_2-u-boot.dtsi
@@ -6,3 +6,7 @@
 #include "socfpga_arria10-handoff.dtsi"
 #include "socfpga_arria10_handoff_u-boot.dtsi"
 #include "socfpga_arria10_mercury_aa1-u-boot.dtsi"
+
+&fpga_mgr {
+	altr,bitstream = "fpga-480-2.itb";
+};
-- 
2.37.2.672.g94769d06f0-goog


  parent reply	other threads:[~2022-08-26  7:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  7:53 [PATCH 0/4] Update Chameleon v3 configuration Paweł Anikiel
2022-08-26  7:53 ` [PATCH 1/4] socfpga: chameleonv3: Enable ext4 in SPL Paweł Anikiel
2022-08-26 19:39   ` Alexandru M Stan
2022-08-26  7:53 ` [PATCH 2/4] socfpga: chameleonv3: Move environment to a text file Paweł Anikiel
2022-08-26 19:46   ` Alexandru M Stan
2022-08-26  7:53 ` Paweł Anikiel [this message]
2022-08-26 19:48   ` [PATCH 3/4] arm: dts: chameleonv3: Override chameleonv3 bitstream names Alexandru M Stan
2022-08-30  2:30   ` Simon Glass
2022-08-26  7:53 ` [PATCH 4/4] arm: dts: chameleonv3: Add 270-2 variant Paweł Anikiel
2022-08-27  0:20   ` Simon Glass
2022-08-29  8:23     ` Paweł Anikiel
2022-08-30  2:29       ` Simon Glass
2022-08-30  3:12         ` Alexandru M Stan
2022-08-30 11:51           ` Paweł Anikiel
2022-08-30 15:56             ` Simon Glass
2022-09-02 13:16               ` Paweł Anikiel
2022-09-02 19:59                 ` Simon Glass
2022-09-05 10:25                   ` Paweł Anikiel

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=20220826075317.1888714-4-pan@semihalf.com \
    --to=pan@semihalf.com \
    --cc=amstan@chromium.org \
    --cc=ka@semihalf.com \
    --cc=marex@denx.de \
    --cc=mw@semihalf.com \
    --cc=simon.k.r.goldschmidt@gmail.com \
    --cc=sjg@chromium.org \
    --cc=tien.fong.chee@intel.com \
    --cc=u-boot@lists.denx.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;
as well as URLs for NNTP newsgroup(s).