From: Douglas Lopes Pereira <douglaslopespereira@gmail.com>
To: Brad Midgley <bmidgley@gmail.com>, linux-bluetooth@vger.kernel.org
Subject: Re: choppy audio on ARM
Date: Tue, 15 Sep 2009 15:14:29 -0300 [thread overview]
Message-ID: <e0ab60670909151114k402c4a33p74c5017d2376315@mail.gmail.com> (raw)
In-Reply-To: <d89ddf300909151000w572c840fo2a59afd0b950230c@mail.gmail.com>
Hi Brad
On Tue, Sep 15, 2009 at 2:00 PM, Brad Midgley <bmidgley@gmail.com> wrote:
> Douglas,
>
> run "lsusb" from a shell after the adapters are all connected.
>
> Brad
>
> On Tue, Sep 15, 2009 at 7:14 AM, Douglas Lopes Pereira
> <douglaslopespereira@gmail.com> wrote:
>> Hi Brad,
>>
>> On Mon, Sep 14, 2009 at 5:47 PM, Brad Midgley <bmidgley@gmail.com> wrote:
>>> Douglas
>>>
>>>> - Connecting bluetooth dongle over USB Hub:
>>>>
>>>> usb 1-1: new high speed USB device using orion-ehci and address 19
>>>> usb 1-1: configuration #1 chosen from 1 choice
>>>> hub 1-1:1.0: USB hub found
>>>> hub 1-1:1.0: 4 ports detected
>>>> usb 1-1.3: new full speed USB device using orion-ehci and address 20
>>>> usb 1-1.3: configuration #1 chosen from 1 choice
>>>>
>>>> - Connecting bluetooth directly on Sheeva Plug:
>>>>
>>>> usb 1-1: new full speed USB device using orion-ehci and address 14
>>>> usb 1-1: configuration #1 chosen from 1 choice
>>>
>>> "lsusb" in both cases should shed more light on the topology and where
>>> full speed links creep in.
>>>
>>> --
>>> Brad Midgley
>>>
>>
>> Could you elaborate a little bit more on that?
>>
>> Thank you.
>>
>
>
>
> --
> Brad Midgley
>
This is the output from lsusb. No interesting information in my point of view:
- Connecting bluetooth directly on Sheeva Plug:
Bus 001 Device 014: ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Connecting bluetooth dongle over USB Hub:
Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode)
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc. USB 2.0 Hub /
D-Link DUB-H4 USB 2.0 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Can you or someone else cite differences between EHCI driver handling
the usb dongle over the usb hub or directly connected?
Thank you for your patience and attention.
Douglas
prev parent reply other threads:[~2009-09-15 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:42 choppy audio on ARM Rafael Seste
2009-09-14 18:17 ` Douglas Lopes Pereira
2009-09-14 20:47 ` Brad Midgley
2009-09-15 13:14 ` Douglas Lopes Pereira
[not found] ` <d89ddf300909151000w572c840fo2a59afd0b950230c@mail.gmail.com>
2009-09-15 18:14 ` Douglas Lopes Pereira [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=e0ab60670909151114k402c4a33p74c5017d2376315@mail.gmail.com \
--to=douglaslopespereira@gmail.com \
--cc=bmidgley@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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