From: Arkadiusz Bokowy <arkadiusz.bokowy@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames
Date: Wed, 27 Aug 2025 17:02:01 +0200 [thread overview]
Message-ID: <CAGFh026z9qhAzLOnBUPGojtuO5dH497DppLxiA++-9=odBohbg@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZKorYK7MKUr1DsipZOUbkNuecW4WpbVKtjyb5ha5EnrSQ@mail.gmail.com>
> Looks like we are missing:
>
> + /* Barrot Technology Bluetooth devices */
> + { USB_DEVICE(0x33fa, 0x0010), .driver_info = BTUSB_BARROT },
> + { USB_DEVICE(0x33fa, 0x0012), .driver_info = BTUSB_BARROT },
>
> We can probably add it together in the same patch, so we don't have to
> rely on Fixes to inform the changes below needs to go together, but
> then we should include the contents of /sys/kernel/debug/usb/devices
> before the information why we need the changes to detect extra bytes
> in order for it to work.
OK, so, should I restore the quirk (so this check is only for Barrot
devices)? Or add driver_info = BARROT without actually using it
anywhere?
next prev parent reply other threads:[~2025-08-27 15:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 17:25 [PATCH] Bluetooth: btusb: Fixup quirk for reading ext features on some Barrot controllers Arkadiusz Bokowy
2025-08-25 17:44 ` Paul Menzel
2025-08-25 17:59 ` bluez.test.bot
2025-08-25 18:32 ` [PATCH] " Luiz Augusto von Dentz
2025-08-25 18:49 ` Arkadiusz Bokowy
2025-08-25 18:56 ` Luiz Augusto von Dentz
2025-08-25 19:37 ` Arkadiusz Bokowy
2025-08-25 20:08 ` Luiz Augusto von Dentz
2025-08-25 20:16 ` Arkadiusz Bokowy
2025-08-26 4:44 ` Arkadiusz Bokowy
2025-08-26 13:45 ` Luiz Augusto von Dentz
2025-08-26 16:23 ` Arkadiusz Bokowy
2025-08-26 16:36 ` Luiz Augusto von Dentz
2025-08-26 17:03 ` [PATCH v2] Bluetooth: btusb: Check for unexpected bytes when defragmenting HCI frames Arkadiusz Bokowy
2025-08-26 17:33 ` [v2] " bluez.test.bot
2025-08-26 19:31 ` [PATCH v2] " Luiz Augusto von Dentz
2025-08-27 13:42 ` Luiz Augusto von Dentz
2025-08-27 15:02 ` Arkadiusz Bokowy [this message]
2025-08-27 15:20 ` Luiz Augusto von Dentz
2025-08-27 16:40 ` [PATCH v3] " Arkadiusz Bokowy
2025-08-27 17:05 ` [v3] " bluez.test.bot
2025-08-27 6:03 ` [PATCH v2] " Paul Menzel
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='CAGFh026z9qhAzLOnBUPGojtuO5dH497DppLxiA++-9=odBohbg@mail.gmail.com' \
--to=arkadiusz.bokowy@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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;
as well as URLs for NNTP newsgroup(s).