From: Georg Gottleuber <g.gottleuber@tuxedocomputers.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
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:24:27 +0100 [thread overview]
Message-ID: <129bf442-2505-41c8-9254-ad7cacefab89@tuxedocomputers.com> (raw)
In-Reply-To: <5hvghahezqms6x4pi3acgaujyhiql6mzl2xhzph5phhki2yiyq@oi3xjatj7r64>
[-- Attachment #1: Type: text/plain, Size: 860 bytes --]
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.
Best regards,
Georg
[-- Attachment #2: dmesg_loading_zap.log --]
[-- Type: text/x-log, Size: 2271 bytes --]
[ 38.585691] firmware_class:fw_log_firmware_info: msm_dpu ae01000.display-controller: Loaded FW: qcom/gen70500_sqe.fw, sha256: 05ae89e6dea62268cec3f4abb5d7d6db2c95270ff105fd056f77262e39d2e527
[ 38.585693] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/gen70500_sqe.fw from new location
[ 38.585708] firmware_class:__allocate_fw_priv: firmware_class: __allocate_fw_priv: fw-qcom/gen70500_gmu.bin fw_priv=0000000025167cab
[ 38.585816] firmware_class:fw_get_filesystem_firmware: msm_dpu ae01000.display-controller: Loading firmware from /lib/firmware/qcom/gen70500_gmu.bin
[ 38.585818] firmware_class:fw_get_filesystem_firmware: msm_dpu ae01000.display-controller: direct-loading qcom/gen70500_gmu.bin
[ 38.585819] firmware_class:fw_set_page_data: firmware_class: fw_set_page_data: fw-qcom/gen70500_gmu.bin fw_priv=0000000025167cab data=00000000e91785a9 size=81312
[ 38.585856] firmware_class:fw_log_firmware_info: msm_dpu ae01000.display-controller: Loaded FW: qcom/gen70500_gmu.bin, sha256: 5dfba247d548cabcb892ffa716e8dc82a345fd54b5dbae46ba523230e7ae37dd
[ 38.585858] msm_dpu ae01000.display-controller: [drm:adreno_request_fw [msm]] loaded qcom/gen70500_gmu.bin from new location
[ 38.588671] [drm] Loaded GMU firmware v4.3.17
[ 38.653154] firmware_class:__allocate_fw_priv: firmware_class: __allocate_fw_priv: fw-qcom/x1e80100/gen70500_zap.mbn fw_priv=0000000023d4bdba
[ 38.653329] firmware_class:fw_get_filesystem_firmware: msm_dpu ae01000.display-controller: Loading firmware from /lib/firmware/qcom/x1e80100/gen70500_zap.mbn
[ 38.653331] firmware_class:fw_get_filesystem_firmware: msm_dpu ae01000.display-controller: direct-loading qcom/x1e80100/gen70500_zap.mbn
[ 38.653333] firmware_class:fw_set_page_data: firmware_class: fw_set_page_data: fw-qcom/x1e80100/gen70500_zap.mbn fw_priv=0000000023d4bdba data=000000002768b5f9 size=12088
[ 38.653344] firmware_class:fw_log_firmware_info: msm_dpu ae01000.display-controller: Loaded FW: qcom/x1e80100/gen70500_zap.mbn, sha256: abaef5222856ce976014512d40f87d63b380a604dbb095c469f02feb924e0b26
[ 38.657789] firmware_class:__free_fw_priv: firmware_class: __free_fw_priv: fw-qcom/x1e80100/gen70500_zap.mbn fw_priv=0000000023d4bdba data=000000002768b5f9 size=12088
next prev parent reply other threads:[~2025-03-18 15:24 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 [this message]
2025-03-18 15:57 ` Konrad Dybcio
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=129bf442-2505-41c8-9254-ad7cacefab89@tuxedocomputers.com \
--to=g.gottleuber@tuxedocomputers.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=ggo@tuxedocomputers.com \
--cc=konrad.dybcio@oss.qualcomm.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