From: Stevie Trujillo <stevie.trujillo@gmail.com>
To: Hui Wang <hui.wang@canonical.com>
Cc: marcel@holtmann.org, tedd.an@intel.com, linux-bluetooth@vger.kernel.org
Subject: Re: Intel 7260 bluetooth malfunction when it is connected to EHCI bus
Date: Thu, 7 Nov 2013 11:07:19 +0100 [thread overview]
Message-ID: <20131107110719.445e8e6f@localhost> (raw)
In-Reply-To: <527B0CF1.7010703@canonical.com>
On Thu, 07 Nov 2013 11:45:53 +0800
Hui Wang <hui.wang@canonical.com> wrote:
> Do you know any tools can decode the log generated by usbmon?
Hmm, I never actually used the usbmon program. I did "modprobe usbmon",
then Wireshark shows usbmon{1..4} (one for each bus) as an interface
like eth0 for ethernet. http://wiki.wireshark.org/CaptureSetup/USB
If it's difficult to compare two captures in Wireshark (I don't know any
other method than visual inspection), tshark (Wireshark's "command-line
counter-part") is able to decode to stdout. Maybe one can run the diff
program on that. The output seems a bit terse however.
Please be aware: in my Wireshark (1.10.2) one of the of the SCO setup
packets are decoded slightly wrong. It looks like Wireshark is missing
a BDADDR in the beginning, so all the other fields get shifted.
next prev parent reply other threads:[~2013-11-07 10:07 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 [this message]
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
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=20131107110719.445e8e6f@localhost \
--to=stevie.trujillo@gmail.com \
--cc=hui.wang@canonical.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.