From: Stevie Trujillo <stevie.trujillo@gmail.com>
To: Michal Labedzki <michal.labedzki@tieto.com>
Cc: Hui Wang <hui.wang@canonical.com>,
Marcel Holtmann <marcel@holtmann.org>,
tedd.an@intel.com,
"linux-bluetooth@vger.kernel.org development"
<linux-bluetooth@vger.kernel.org>
Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus
Date: Fri, 20 Dec 2013 13:30:01 +0100 [thread overview]
Message-ID: <20131220133001.36d5e7aa@localhost> (raw)
In-Reply-To: <CALkxMhFBoJO+_1PRQhS-a9g8qQW_Vc+7Ss6HG6P8i0DDoeZYmw@mail.gmail.com>
On Tue, 26 Nov 2013 10:11:47 +0100
Michal Labedzki <michal.labedzki@tieto.com> wrote:
> Bug is now fixed in "svn path=/trunk/; revision=53525". You can wait
> for next development (1.11.3) or stable (1.12), however you can build
> Wireshark from sources (should be easy - like BlueZ: git clone
> http://code.wireshark.org/git/wireshark; ./autogen; ./configure; make;
> ./wireshark) or via "private" sources like:
> $ sudo add-apt-repository ppa:dreibh/ppa
> $ sudo apt-get update
> $ sudo apt-get install wireshark
Thank you! I was busy failing exams and I didn't get to filing the
bug report.
I will try it out after xmas. I bought an $1 Bluetooth USB which seems
to do SCO fine, but it usually dies after a few minutes (with
Bluetooth: hci0 command {0x1009,0x0419,etc} tx timeout).
I took a quick look in wireshark, comparing this USB thing vs Intel,
it seems like they set up SCO in a different way. I think the USB stick
might be Bluetooth 2.0 (despite the decription saying Bluetooth 2.1).
prev parent reply other threads:[~2013-12-20 12:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 10:03 Intel 7260 bluetooth malfunction when it is connected to EHCI bus Hui Wang
2013-10-29 11:16 ` Marcel Holtmann
2013-10-30 2:51 ` Hui Wang
2013-10-30 19:36 ` Tedd Ho-Jeong An
2013-10-31 5:15 ` Hui Wang
2013-10-30 19:44 ` Marcel Holtmann
2013-10-31 5:29 ` Hui Wang
2013-10-31 9:49 ` Marcel Holtmann
2013-11-01 2:39 ` Hui Wang
2013-11-01 7:49 ` Marcel Holtmann
2013-11-01 9:18 ` Hui Wang
2013-11-02 19:05 ` Marcel Holtmann
2013-11-04 5:59 ` Hui Wang
2013-11-04 13:15 ` Stevie Trujillo
2013-11-05 2:32 ` Hui Wang
2013-11-05 18:44 ` Stevie Trujillo
2013-11-07 3:45 ` Hui Wang
2013-11-07 10:07 ` Stevie Trujillo
2013-11-08 1:43 ` Hui Wang
2013-11-08 11:17 ` Michal Labedzki
2013-11-26 9:11 ` Michal Labedzki
2013-12-20 12:30 ` Stevie Trujillo [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=20131220133001.36d5e7aa@localhost \
--to=stevie.trujillo@gmail.com \
--cc=hui.wang@canonical.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=michal.labedzki@tieto.com \
--cc=tedd.an@intel.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