From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Roger Shimizu <rosh@debian.org>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@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
Subject: Re: [PATCH] arm64: dts: qcom: qcs6490: Add Thundercomm AI Mini PC G1 IoT
Date: Thu, 12 Feb 2026 10:04:51 +0100 [thread overview]
Message-ID: <f8016c0b-1e64-412c-a8a7-e09eb677e35d@oss.qualcomm.com> (raw)
In-Reply-To: <CAEQ9gE=p_94p5Rnn===2qMq9MNUePbGaRgJkbkoLXg6X5oywvA@mail.gmail.com>
On 2/11/26 8:27 AM, Roger Shimizu wrote:
> On Mon, Feb 9, 2026 at 12:31 AM Konrad Dybcio
> <konrad.dybcio@oss.qualcomm.com> wrote:
>>
>> It may be that your version of pydtschema is wildly out of date.
>>
>> Nowadays the general expectation for using bleeding-edge python
>> tools seems to be for one to grab them via pipx
>
> Thanks for the info!
> Sorry I forgot to mention that I spent some time last weekend, and
> resolved the issue in Debian [1]. (patch was enclosed in the ticket)
> I prefer to use deb pkg, over pip install.
Thanks for being an active contributor!
Konrad
>
> Now I'm using locally built dt-schema deb pkg (updated to latest tag
> 2025.12), and and run "make dt_binding_check" successfully.
>
> [1] https://bugs.debian.org/1127460
>
> -Roger
prev parent reply other threads:[~2026-02-12 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 10:31 [PATCH] arm64: dts: qcom: qcs6490: Add Thundercomm AI Mini PC G1 IoT Roger Shimizu
2026-02-04 2:51 ` Dmitry Baryshkov
2026-02-04 8:53 ` Roger Shimizu
2026-02-04 9:20 ` Konrad Dybcio
2026-02-05 0:04 ` Roger Shimizu
2026-02-05 8:52 ` Konrad Dybcio
2026-02-06 9:35 ` Roger Shimizu
2026-02-06 9:41 ` Krzysztof Kozlowski
2026-02-06 9:55 ` Roger Shimizu
2026-02-06 9:57 ` Konrad Dybcio
2026-02-07 5:46 ` Roger Shimizu
2026-02-09 8:31 ` Konrad Dybcio
2026-02-11 7:27 ` Roger Shimizu
2026-02-12 9:04 ` Konrad Dybcio [this message]
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=f8016c0b-1e64-412c-a8a7-e09eb677e35d@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=rosh@debian.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