From: Thomas Arendsen Hein <thomas@intevation.de>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Blootooth 2.0 devices
Date: Mon, 17 Jul 2006 08:59:32 +0200 [thread overview]
Message-ID: <20060717065932.GA7218@intevation.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0607171648260.1625@data.home>
* Geoff Shang <geoff@hitsandpieces.net> [20060717 08:56]:
> Just purchasing some USB bluetooth dongles and wondered how well if at all
> BlueTooth 2.0 was supported in the BlueZ stack. If not, what is the most
> recent revision of the Bluetooth standard that is supported?
2.0 is supported for quite a while now. I use a CSR-based one with
the bluez packages for Debian sarge, which are already somewhat old.
> I'm currently using two Bluetooth 1.1 CSR-based dongles and want to get a
> higher data rate on my PAN. Will going up to a 1.2 dongle achieve any
> speed increase or do I need to make the move to a Bluetooth 2 dongle?
1.2 isn't faster, so I'd recommend buying a 2.0 dongle. See the list
archive for recommended types.
Thomas
--
Email: thomas@intevation.de
http://intevation.de/~thomas/
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2006-07-17 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 6:56 [Bluez-users] Blootooth 2.0 devices Geoff Shang
2006-07-17 6:59 ` Thomas Arendsen Hein [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=20060717065932.GA7218@intevation.de \
--to=thomas@intevation.de \
--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).