From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Georg Gottleuber <ggo@tuxedocomputers.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, wse@tuxedocomputers.com,
cs@tuxedocomputers.com
Subject: Re: [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1
Date: Tue, 18 Mar 2025 16:57:34 +0100 [thread overview]
Message-ID: <66049cc8-3e4d-4d5e-8ff9-67b408e5b1a1@oss.qualcomm.com> (raw)
In-Reply-To: <129bf442-2505-41c8-9254-ad7cacefab89@tuxedocomputers.com>
On 3/18/25 4:24 PM, Georg Gottleuber wrote:
> Am 07.03.25 um 07:45 schrieb Dmitry Baryshkov:
> [...]
>>>> diff --git a/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
>>>> new file mode 100644
>>>> index 000000000000..86bdec4a2dd8
>>>> --- /dev/null
>>>> +++ b/arch/arm64/boot/dts/qcom/x1e80100-tuxedo-elite-14-gen1.dts
>>>
>>>> +&gpu {
>>>> + status = "okay";
>>>> +
>>>> + zap-shader {
>>>> + firmware-name = "qcom/a740_zap.mbn";
>>>
>>> Are the laptop's OEM key/security fuses not blown?
>>
>> Can this laptop use "qcom/x1e80100/gen70500_zap.mbn" which is already a
>> part of linux-firmware?
>
> It seems so.
>
> Because there were no logs about loading zap.mbn, I activated dyndbg
> (dyndbg="file drivers/base/firmware_loader/main.c +fmp"). See attachment
> for dmesg output. But GUI freezes after sddm login.
Okay, have you updated mesa to something recent? Try the current state of
main branch
Konrad
next prev parent reply other threads:[~2025-03-18 15:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 12:25 [PATCH] arm64: dts: qcom: Add device tree for TUXEDO Elite 14 Gen1 Georg Gottleuber
2025-03-06 12:41 ` Krzysztof Kozlowski
2025-03-06 13:56 ` Georg Gottleuber
2025-03-06 14:03 ` Krzysztof Kozlowski
2025-03-06 16:45 ` Dmitry Baryshkov
2025-03-06 12:50 ` Konrad Dybcio
2025-03-06 15:22 ` Georg Gottleuber
2025-03-06 18:15 ` Konrad Dybcio
2025-03-06 19:30 ` Michael Srba
2025-03-07 6:45 ` Dmitry Baryshkov
2025-03-18 15:24 ` Georg Gottleuber
2025-03-18 15:57 ` Konrad Dybcio [this message]
2025-03-18 17:17 ` Rob Clark
2025-03-18 21:36 ` Dmitry Baryshkov
2025-03-21 15:49 ` Ettore Chimenti
2025-03-21 15:51 ` Dmitry Baryshkov
2025-03-28 11:34 ` Georg Gottleuber
2025-03-28 12:42 ` Dmitry Baryshkov
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=66049cc8-3e4d-4d5e-8ff9-67b408e5b1a1@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cs@tuxedocomputers.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=g.gottleuber@tuxedocomputers.com \
--cc=ggo@tuxedocomputers.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=wse@tuxedocomputers.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