uboot: Bump uboot version to 2026.07-rc1#2016
uboot: Bump uboot version to 2026.07-rc1#2016aswinm94 wants to merge 2 commits intoqualcomm-linux:masterfrom
Conversation
aswinm94
requested review from
anujm1,
koenkooi,
lumag,
ndechesne,
ricardosalveti,
sbanerjee-quic and
vkraleti
as code owners
Test run workflowTest jobs for commit 11e7c64
All jobs summary
|
Test Results 95 files ± 0 479 suites ±0 6h 23m 54s ⏱️ + 11m 45s For more details on these failures, see this check. Results for commit 0596725. ± Comparison against base commit 517d87f. ♻️ This comment has been updated with latest results. |
|
Please rebase. |
|
NAK for this U-Boot bump since it's based on a downstream U-Boot branch: https://github.com/qualcomm-linux/u-boot/commits/u-boot-mainline-1.0/ and not on qcom-next. @aswinm94 didn't we discussed about that the meta-qcom integration has to closely follow U-Boot upstream and not a dump of downstream patches. |
| @@ -0,0 +1 @@ | |||
| # CONFIG_TOOLS_MKEFICAPSULE is not set | |||
There was a problem hiding this comment.
Please point to the discussion reported in u-boot and oe-core as part of the commit.
There was a problem hiding this comment.
Added the discussion thread as part of commit
the srcrev has been updated to point to qcom-next |
Update the uboot version from 2026.04-rc1 to stable 2026.07-rc1 release Signed-off-by: Aswin Murugan <aswin.murugan@oss.qualcomm.com>
aswinm94
changed the title
The mkeficapsule host tool fails to compile with U-Boot v2026.04+ in Yocto builds. This is a known upstream issue already reported in U-Boot and OE-Core. As OE-Core has not yet been updated to support v2026.04, disable CONFIG_TOOLS_MKEFICAPSULE to unblock the build. This change is intended as a temporary workaround until the upstream fixes are merged and consumed. References: - https://lore.kernel.org/all/20260408130553.819420-1-fra.schnyder@gmail.com/ - https://lore.kernel.org/u-boot/20260409074710.1322519-1-Wojciech.Dubowik@mt.com/ Signed-off-by: Aswin Murugan <aswin.murugan@oss.qualcomm.com>
|
Since uboot qcom-nxt branch has been rebased to 2026.07-rc1 recently, updated the PR to align with it |
Bump to qcom-next based on 2026.07-rc1 sounds fine to me. |
|
But why are you updating to a newer version after this PR was proposed and approved? Since this is a major change I would prefer updating in steps, first to the final 04 release and then to the 07-rc1 (since this is rc1 and it might have other issues). |
@ricardosalveti , when the PR was created the qcom-next branch was based on 2026.04, yesterday we had a 2026.07-rc1 release from uboot which has many of the changes from Qualcomm also the qcom-next branch was rebased to the newer version, hence i updated PR to point to 2026.07-rc1 |
Sure, but please avoid changing PRs which were already approved for the previous release, it is perfectly fine to propose a new one later for the new bump, which also helps when we want to bisect possible regressions and issues. |
5 participants
Update the uboot version from 2026.04-rc1 to 2026.07-rc1 release
U-Boot v2026.04 introduces a build failure in the mkeficapsule host tool
when building via Yocto/OpenEmbedded.
This is a known upstream issue reported in both U-Boot and OE-Core,
and the required fixes are not yet present in the OpenEmbedded layer,
which has not been updated to fully support v2026.04.
As a temporary workaround, CONFIG_TOOLS_MKEFICAPSULE is disabled to
allow the U-Boot build to succeed until the upstream fixes are
available and integrated.