From: Marcel Holtmann <marcel@holtmann.org>
To: Albert Pool <albertpool@solcon.nl>
Cc: Gustavo Padovan <padovan@profusion.mobi>,
linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v3] Add USB ID of HP's Broadcom BCM2035 Bluetooth
Date: Tue, 27 Dec 2011 11:07:29 -0800 [thread overview]
Message-ID: <1325012849.1965.273.camel@aeonflux> (raw)
In-Reply-To: <1325012535.2109.10.camel@albert-ASUSTeK-P4P800SE>
Hi Albert,
please refrain from top-posting on this mailing list.
> I think the desktop's dongle might be to blame when the old laptop fails
> to pair to that. I've had more Bluetooth problems on the desktop, e.g.
> being unable to remove paired devices of the dongle's previous owner.
>
> The Bluetooth sticker on the downside of the old laptop lists:
> Broadcom BCM92035NMD CE 370653-003
> Universal Scientific Industrial
> Contains FCC ID: QDS-BRCM1009
> IC: 4324A-BRCM1009
> SCT: RCPBRBC04-389
> CMI ID: 2003DJ1517
> CNC 16-3215
> along with a lot of text in other languages.
>
> Other BCM2035 USB ID's have BTUSB_WRONG_SCO_MTU but that option really
> does not work reliably on this old laptop.
The need for WRONG_SCO_MTU detail can be easily determined. Check the
output of hciconfig without this quirk. If the SCO MTU essentially shows
0 values, then you need it.
But then again, you are just randomly adding quirks without
understanding what they are for. This makes me worry a lot.
Are you actually running a recent 3.x kernel or are you just using an
outdated kernel?
Regards
Marcel
next prev parent reply other threads:[~2011-12-27 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-24 12:01 [PATCH v3] Add USB ID of HP's Broadcom BCM2035 Bluetooth Albert Pool
2011-12-27 16:03 ` Gustavo Padovan
2011-12-27 17:54 ` Marcel Holtmann
2011-12-27 19:02 ` Albert Pool
2011-12-27 19:07 ` Marcel Holtmann [this message]
2011-12-27 20:30 ` [PATCH v3] Add USB ID of HP's Broadcom BCM2035 Bluetooth [SOLVED] Albert Pool
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=1325012849.1965.273.camel@aeonflux \
--to=marcel@holtmann.org \
--cc=albertpool@solcon.nl \
--cc=linux-bluetooth@vger.kernel.org \
--cc=padovan@profusion.mobi \
/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).