From: Johan Hovold <johan@kernel.org>
To: Jens Glathe <jens.glathe@oldschoolsolutions.biz>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
Zijun Hu <quic_zijuhu@quicinc.com>,
Marcel Holtmann <marcel@holtmann.org>,
Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
Zijun Hu <zijun_hu@icloud.com>,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Andersson <bjorande@quicinc.com>,
Aiqun Yu <quic_aiquny@quicinc.com>,
Cheng Jiang <quic_chejiang@quicinc.com>,
Steev Klimaszewski <steev@kali.org>
Subject: Re: [PATCH] Bluetooth: qca: Support downloading board id specific NVM for WCN6855
Date: Fri, 15 Nov 2024 11:07:56 +0100 [thread overview]
Message-ID: <ZzcdfD9cXuINU8m0@hovoldconsulting.com> (raw)
In-Reply-To: <4186566a-0aa5-4413-96df-fb1b7ebd9db2@oldschoolsolutions.biz>
On Fri, Nov 15, 2024 at 08:13:55AM +0100, Jens Glathe wrote:
> The variant *g* is a SoC variant with some extended capabilities as it
> seems. The X13s doesn't have it, the Windows Dev Kit 2023 and the HP
> Omnibook X14 have it.
Actually my X13s has the GF (or g) variant, so perhaps also other
machines can come with one or the other.
Understanding what the difference is between GF and non-GF would indeed
be interesting.
Johan
next prev parent reply other threads:[~2024-11-15 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 6:26 [PATCH] Bluetooth: qca: Support downloading board id specific NVM for WCN6855 Zijun Hu
2024-11-14 9:49 ` Paul Menzel
2024-11-15 7:13 ` Jens Glathe
2024-11-15 10:07 ` Johan Hovold [this message]
2024-11-16 16:10 ` quic_zijuhu
2024-11-15 6:40 ` Jens Glathe
2024-11-16 16:14 ` quic_zijuhu
2024-11-15 7:17 ` Steev Klimaszewski
2024-11-16 16:17 ` quic_zijuhu
2024-11-15 10:01 ` Johan Hovold
2024-11-16 16:07 ` quic_zijuhu
2024-11-15 16:40 ` Luiz Augusto von Dentz
2024-11-16 15:57 ` quic_zijuhu
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=ZzcdfD9cXuINU8m0@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=bjorande@quicinc.com \
--cc=jens.glathe@oldschoolsolutions.biz \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=pmenzel@molgen.mpg.de \
--cc=quic_aiquny@quicinc.com \
--cc=quic_chejiang@quicinc.com \
--cc=quic_zijuhu@quicinc.com \
--cc=steev@kali.org \
--cc=zijun_hu@icloud.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