From: Rafael Seste <rseste@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: choppy audio on ARM
Date: Fri, 4 Sep 2009 13:42:46 -0300 [thread overview]
Message-ID: <5d223510909040942u7ee2ae0ds96e1321b1fab24b9@mail.gmail.com> (raw)
Hi all,
A couple of months ago I sent a email about a problem with the
bluetooth audio on a ARM platform. I have a choppy audio on the
incoming stream. I still didn't solve this problem but I found a setup
that this problem doesn't happens.
My ARM device has only one USB port, so I always connect the BT dongle
in this port. Last week I bought a USB hub and plug it into the usb
and the BT dongle in the hub. Miraculously this problem disappeared. I
removed the hub and tried again and the problem returns.
Does anybody has any clue why the USB hub "fixed" this choppy audio???
Does it use a different USB drivers?
tks in advance
--
Rafael S. Seste
next reply other threads:[~2009-09-04 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:42 Rafael Seste [this message]
2009-09-14 18:17 ` choppy audio on ARM 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
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=5d223510909040942u7ee2ae0ds96e1321b1fab24b9@mail.gmail.com \
--to=rseste@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