From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] class 1 bluetooth 1.2 dongles with CSR chipset?
Date: Fri, 30 Sep 2005 15:33:53 +0200 [thread overview]
Message-ID: <1128087233.4955.43.camel@localhost.localdomain> (raw)
In-Reply-To: <20050930124108.GA26157@intevation.de>
Hi Thomas,
> I just bought an Anubis Typhoon Bluetooth V1.2 USB adapter, which
> according to the product page http://www.typhoon.de/en/art.php?p=838
> should have "Main chip - CSR BlueCore", but in reality it is a
> Broadcom BCM2035 :-/
>
> It seems to work without problems and without needing to load
> firmware, but I'm a little disappointed because I searched a long
> time trying to find a bluetooth 1.2 class 1 device with CSR chipset.
>
> Aren't there any manufacturers today who sell CSR based USB dongles?
>
> I'm tempted to return it to the store, but what to buy instead?
try to get a Cellink BlueCore4 based dongle with EDR support.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-09-30 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 12:41 [Bluez-users] class 1 bluetooth 1.2 dongles with CSR chipset? Thomas Arendsen Hein
2005-09-30 13:33 ` Marcel Holtmann [this message]
2005-09-30 16:59 ` [Bluez-users] " Thomas Arendsen Hein
2005-10-01 9:12 ` Marcel Holtmann
2005-10-05 15:29 ` Thomas Arendsen Hein
2005-10-05 17:50 ` Marcel Holtmann
2005-09-30 22:16 ` [Bluez-users] " Christian Schuglitsch
2005-10-13 21:24 ` Christian Schuglitsch
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 16:36 Robert Wlaschin
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=1128087233.4955.43.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--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).