From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] CSR BlueCore4 dongles
Date: Wed, 19 Jul 2006 17:47:56 -0600 [thread overview]
Message-ID: <44BEC4AC.4050203@xmission.com> (raw)
In-Reply-To: <200607200028.47928.info@david-geiger.de>
David
> I was just doing an internet search on USB bluetooth dongles and would be
> happy to get some feed-back on the results.
>
> My requirements were:
> - CSR BlueCore4 (as I have heard it is best supported with btsco)
> - Class1
> Are there any other important criteria?
>
> The only devices I have found are:
> - Level One MDU-0025USB (A2DP, USB 1.1)
> - B-Speech Data speed (A2DP)
> - Cellink BTA-6030 (USB 2.0)
> - EPoX BT-DG07A+ (A2DP?)
> - Bluetake BT007EX (A2DP, USB 1.1)
>
> Any experiences with one of the devices or additions are welcome! :)
the bt007ex is a nice adapter. it's also just about the only one that is
easy to find in the US but that doesn't necessarily mean you'll find it
in Germany. fwiw, it includes a2dp drivers for xp that we've used for
testing interoperation (the w2k driver wouldn't work for me)
> There are a few questions left, maybe someone can help me here:
> - Does the dongle explicitely have to support A2DP?
when a dongle is advertised to support a2dp, it either means that you
can add a driver that provides a2dp or that such a driver is included
for windows. every dongle should support a2dp as long as it's not
seriously broken, so it really doesn't mean anything.
> - What is an "AV profile"? Almost all websites list the "Advanced Audio
> Distribution Profile" as an AV profile and say Windows only. Does that mean
> it doesn't support A2DP on linux?
this only relates to windows drivers. you can drive a2dp from linux
(such as we have it)
> http://www.b-speech.de/en/produkt-information/stereo-headsets-und-adapter/b-speech_data-speed/
> - Does it make sense to buy a dongle with USB 2.0 support? The USB 1.1
> datarate is already 12mbit/s which should be enough by far.
the only real reason for usb2 is coexistence with other usb2 devices on
the same bus. the bus has to fall back to usb1 speeds when a usb1 device
on the bus is active.
brad
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-07-19 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 22:28 [Bluez-users] CSR BlueCore4 dongles David Geiger
2006-07-19 23:47 ` Brad Midgley [this message]
2006-07-20 7:04 ` Per Thomas Jahr
2006-07-20 15:52 ` Wolfgang Mües
2006-07-20 16:17 ` Brad Midgley
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=44BEC4AC.4050203@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-users@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).