From: "Michał Kępień" <kernel@kempniu.pl>
To: Pauli Virtanen <pav@iki.fi>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Bluetooth: btusb: check SCO MTU before enabling USB ALT 3 for WBS
Date: Thu, 22 Jul 2021 16:42:12 +0200 [thread overview]
Message-ID: <YPmDxETlABDcAXXF@larwa.hq.kempniu.pl> (raw)
In-Reply-To: <f32df70b9aaccfbb471a6305c5b4884ae14dede3.camel@iki.fi>
Pauli,
> Thanks for testing! What userspace software did you use? Pulseaudio at
> least I think had assumption that mtu <= 60, which breaks here
> (Pipewire works, don't know about bluez-alsa). If otherwise, maybe it
> then needs also the manufacturer flag.
I am using Pipewire 0.3.32.
When I wrote "this adapter (...) reports an SCO MTU of 96 bytes" in my
previous message, I meant that this was the value present in
hdev->sco_mtu around the problematic code location. If this was the
wrong thing to take a look at, please let me know.
--
Best regards,
Michał Kępień
next prev parent reply other threads:[~2021-07-22 14:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 17:58 [PATCH] Bluetooth: btusb: check SCO MTU before enabling USB ALT 3 for WBS Pauli Virtanen
2021-07-16 19:16 ` bluez.test.bot
2021-07-17 13:34 ` [PATCH] " Joseph Hwang
2021-07-21 15:40 ` Pauli Virtanen
2021-07-22 10:28 ` Hilda Wu
2021-07-20 9:15 ` Pasi Kärkkäinen
2021-07-22 13:29 ` Michał Kępień
2021-07-22 14:26 ` Pauli Virtanen
2021-07-22 14:42 ` Michał Kępień [this message]
2021-07-23 10:07 ` [PATCH v2] Bluetooth: btusb: check conditions " Pauli Virtanen
2021-07-23 12:19 ` Marcel Holtmann
2021-07-25 5:47 ` Michał Kępień
2021-08-10 16:48 ` Pasi Kärkkäinen
2021-08-10 18:37 ` Luiz Augusto von Dentz
2021-07-26 18:02 ` [PATCH v3] " Pauli Virtanen
2021-07-27 2:11 ` [v3] " bluez.test.bot
2021-07-30 12:35 ` [PATCH v3] " Pasi Kärkkäinen
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=YPmDxETlABDcAXXF@larwa.hq.kempniu.pl \
--to=kernel@kempniu.pl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=pav@iki.fi \
/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).