From: Akhilesh Nema <nemaakhilesh@gmail.com>
To: buildroot@buildroot.org
Cc: Akhilesh Nema <nemaakhilesh@gmail.com>,
Brandon Maier <brandon.maier@collins.com>,
Vladimir Oltean <olteanv@gmail.com>
Subject: [Buildroot] [PATCH 5/9] package/qoriq-ddr-phy-binary: bump version to lf-6.18.20-2.0.0
Date: Mon, 6 Jul 2026 21:05:40 -0700 [thread overview]
Message-ID: <20260707040544.108052-5-nemaakhilesh@gmail.com> (raw)
In-Reply-To: <20260707040544.108052-1-nemaakhilesh@gmail.com>
Changelog:
https://github.com/nxp-qoriq/ddr-phy-binary/compare/lf-6.12.34-2.1.0...lf-6.18.20-2.0.0
Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
---
package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.hash | 2 +-
package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.hash b/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.hash
index 6ae08a3152..942c654766 100644
--- a/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.hash
+++ b/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.hash
@@ -1,3 +1,3 @@
# Locally calculated
-sha256 d5a5a9b7f25295e9e41c8e7c18a1986d1b59ebe519113ed6b45ede51639da92f qoriq-ddr-phy-binary-lf-6.12.34-2.1.0.tar.gz
+sha256 d5a5a9b7f25295e9e41c8e7c18a1986d1b59ebe519113ed6b45ede51639da92f qoriq-ddr-phy-binary-lf-6.18.20-2.0.0.tar.gz
sha256 e7e5f4949f7ac9f9a5d4d68b8f835f3ddc93ad47b594a11de699d90b9175413f NXP-Binary-EULA.txt
diff --git a/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.mk b/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.mk
index 04cedbbe00..3c39b36362 100644
--- a/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.mk
+++ b/package/qoriq-ddr-phy-binary/qoriq-ddr-phy-binary.mk
@@ -4,7 +4,7 @@
#
################################################################################
-QORIQ_DDR_PHY_BINARY_VERSION = lf-6.12.34-2.1.0
+QORIQ_DDR_PHY_BINARY_VERSION = lf-6.18.20-2.0.0
QORIQ_DDR_PHY_BINARY_SITE = $(call github,nxp-qoriq,ddr-phy-binary,$(QORIQ_DDR_PHY_BINARY_VERSION))
QORIQ_DDR_PHY_BINARY_LICENSE = NXP Binary EULA
QORIQ_DDR_PHY_BINARY_LICENSE_FILES = NXP-Binary-EULA.txt
--
2.34.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-07-07 4:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 4:05 [Buildroot] [PATCH 1/9] package/fmlib: bump version to lf-6.18.20-2.0.0 Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 2/9] package/qoriq-rcw: bump to version lf-6.18.20-2.0.0 Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 3/9] package/qoriq-fm-ucode: bump version to lf-6.18.20-2.0.0 Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 4/9] package/fmc: " Akhilesh Nema
2026-07-07 4:05 ` Akhilesh Nema [this message]
2026-07-07 4:05 ` [Buildroot] [PATCH 6/9] configs/ls1028a-rdb: bump BSP tag " Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 7/9] configs/ls1043a-rdb: " Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 8/9] configs/ls1046a-frwy: " Akhilesh Nema
2026-07-07 4:05 ` [Buildroot] [PATCH 9/9] configs/ls1046a-rdb: " Akhilesh Nema
2026-07-19 19:29 ` [Buildroot] [PATCH 1/9] package/fmlib: bump version " Julien Olivain via buildroot
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=20260707040544.108052-5-nemaakhilesh@gmail.com \
--to=nemaakhilesh@gmail.com \
--cc=brandon.maier@collins.com \
--cc=buildroot@buildroot.org \
--cc=olteanv@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