From: Stephan Gerhold <stephan@gerhold.net>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] arm64: dts: qcom: msm8916: drop dtbTool compatibles
Date: Thu, 14 Mar 2024 11:17:11 +0100 [thread overview]
Message-ID: <ZfLOp3aGgvGTRsT2@gerhold.net> (raw)
In-Reply-To: <20240314-msm8916-drop-compats-v2-0-5a4b40f832d3@linaro.org>
rOn Thu, Mar 14, 2024 at 03:42:47AM +0200, Dmitry Baryshkov wrote:
> Only two boards ever has adopted the dtbTool-specific compatibles.
> However the dtbTool should not be used anymore. It was required only for
> the old, broken lk1st bootloader. All users of those boards should have
> updated to use lk2nd instead. Otherwise several important features
> (secondary CPU cores, WiFi, BT) will not work with the upstream kernel.
Nitpick: The term "the old, broken lk1st bootloader" is a bit misleading
here. I believe you are referring to Qualcomm's original LK bootloader.
"lk1st" is actually the name of an alternative configuration in the
lk2nd project that can be used to replace the first-stage bootloader on
devices without secure boot, e.g. DB410c and a few smartphones. lk1st
has exactly the same functionality as lk2nd and is therefore definitely
not old and broken. Both support DTB selection, secondary CPU cores etc. :-)
I don't think we put the cover letter into a merge commit message in the
qcom tree, so there is no need to resend. I just wanted to clarify this.
Thanks for cleaning this up!
Stephan
next prev parent reply other threads:[~2024-03-14 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 1:42 [PATCH v2 0/2] arm64: dts: qcom: msm8916: drop dtbTool compatibles Dmitry Baryshkov
2024-03-14 1:42 ` [PATCH v2 1/2] dt-bindings: arm: qcom: drop dtbTool-specific compatibles Dmitry Baryshkov
2024-03-14 7:02 ` Krzysztof Kozlowski
2024-03-14 1:42 ` [PATCH v2 2/2] arm64: dts: qcom: msm8916: " Dmitry Baryshkov
2024-03-14 10:17 ` Stephan Gerhold [this message]
2024-04-04 21:22 ` [PATCH v2 0/2] arm64: dts: qcom: msm8916: drop dtbTool compatibles Bjorn Andersson
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=ZfLOp3aGgvGTRsT2@gerhold.net \
--to=stephan@gerhold.net \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=robh@kernel.org \
/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