mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hex Lindqvist <hex@freenixos.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Bartosz Golaszewski <brgl@kernel.org>,
	Marcel Holtmann <marcel@holtmann.org>,
	Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
	linux-bluetooth@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: qca: Disable SoC debug logging for WCN3990
Date: Fri,  6 Nov 2026 11:29:01 -0800	[thread overview]
Message-ID: <20261106192901.1930168-1-hex@freenixos.com> (raw)
In-Reply-To: <56866622-a854-4aae-9e97-40eecc4adbe1@molgen.mpg.de>

On 06.11.26 11:57, Paul Menzel wrote:
> Does Linux log anything about this? Maybe, also paste an excerpt from
> btmon capture?

No, Linux logs nothing; the packets only show up in btmon:

  = Vendor Diagnostic (len 492)                      [hci0] 0.761331
          dc 2e e8 01 e4 01 03 00 0a ff 10 04 01 00 55 53  ..............US
  = Vendor Diagnostic (len 481)                     [hci0] 11.334015
          dc 2e dd 01 d9 01 04 00 0a ff 10 04 01 00 51 d3  ..............Q.

I will add this to the commit message in v2.

> Both firmware file names are the same. What is the difference?

They are different builds with the same file name:

  OnePlus:        BTFM.CHE.2.1.4.c2-00002-QCACHROMZ-2.184841.1
                  (216380 bytes, built Jan 3 2019, shipped with OxygenOS)
  linux-firmware: BTFM.CHE.2.1.3.c7-00024-QCACHROM-1
                  (177060 bytes, built Dec 4 2018)

Both TLV headers report the same ROM build (0x0201) and patch version
(0x0002), so only the build label tells them apart. The controller
returns the OnePlus label when asked with EDL_GET_BUILD_INFO_CMD;
btqca does not send that for WCN3990, so it is not in the kernel log.

Thank you for the review.

Hex

      reply	other threads:[~2026-11-06 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-05 20:19 Hex Lindqvist
2026-11-06  9:44 ` Bartosz Golaszewski
2026-11-06 10:57 ` Paul Menzel
2026-11-06 19:29   ` Hex Lindqvist [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=20261106192901.1930168-1-hex@freenixos.com \
    --to=hex@freenixos.com \
    --cc=brgl@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --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 \
    /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

all inboxes | Powered by JetHome®