Return-Path: Message-ID: <527C41C5.8070209@canonical.com> Date: Fri, 08 Nov 2013 09:43:33 +0800 From: Hui Wang MIME-Version: 1.0 To: Stevie Trujillo 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 References: <526F8804.9060906@canonical.com> <52707428.9070908@canonical.com> <6091DDC7-7B00-4457-82A0-F8CC9B4EE9DD@holtmann.org> <5271EAA2.1030705@canonical.com> <5273147E.4040004@canonical.com> <527371D4.1010305@canonical.com> <9DFD9618-158E-41C4-8183-134A3FC4E61F@holtmann.org> <527737C7.40208@canonical.com> <20131104141539.772e1636@localhost> <527858A5.2080801@canonical.com> <20131105194431.54fba8fb@localhost> <527B0CF1.7010703@canonical.com> <20131107110719.445e8e6f@localhost> In-Reply-To: <20131107110719.445e8e6f@localhost> Content-Type: text/plain; charset=ISO-8859-1; format=flowed List-ID: On 11/07/2013 06:07 PM, Stevie Trujillo wrote: > On Thu, 07 Nov 2013 11:45:53 +0800 > Hui Wang 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. > > Thanks for sharing this knowledge, i will have a try according to your instructions. Regards, Hui.