linux-kernel - Re: [PATCH v2] arm64: dts: qcom: sm8550: Fix DTBO boot failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d4faaf8d-1517-4187-8801-a2dd52d8dde3@kernel.org>
Date: Sun, 8 Feb 2026 10:07:15 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: webgeek1234@...il.com, Bjorn Andersson <andersson@...nel.org>,
 Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, Kumar Sharma <quic_vksharma@...cinc.com>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
 linux-kernel@...r.kernel.org, Pavan Kondeti <pavan.kondeti@....qualcomm.com>
Subject: Re: [PATCH v2] arm64: dts: qcom: sm8550: Fix DTBO boot failure

On 08/02/2026 02:16, Aaron Kling via B4 Relay wrote:
> From: Pavan Kondeti <pavan.kondeti@....qualcomm.com>
> 
> ABL requires certain things in the base dtb to apply a dtbo. Namely:
> 
> * A label named qcom_tzlog must exist, but doesn't have to contain any
>   specific properties
> * The timer node must have a label named arch_timer
> 
> This aligns the sm8550 soc dtsi with those requirements. Without these
> in the base dtb, when ABL attempts to apply any dtbo, it will fail to
> the bootloader menu.
> 

Incomplete DCO chain.

> Co-authored-by: Aaron Kling <webgeek1234@...il.com>
> Signed-off-by: Aaron Kling <webgeek1234@...il.com>
> ---
> With a current mainline sm8550 base dtb, ABL will fail to apply any dtbo
> and fail back to the bootloader menu. There are two changes needed:

Since when? We were testing SM8550 (me on QRD) all the time and there
was no problem.

You need to provide details which hardware needs it, if this is about to
expected, but honestly, we don't add such nodes/labels for downstream
bootloader. Qualcomm should fix the bootloder instead.


Best regards,
Krzysztof