From: Marcel Holtmann <marcel@holtmann.org>
To: Rene Mayrhofer <rene@soft.uni-linz.ac.at>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Re: command tx timeout and continuous inquiry.
Date: 13 Oct 2003 11:19:45 +0200 [thread overview]
Message-ID: <1066036791.14513.186.camel@pegasus> (raw)
In-Reply-To: <3F8A7E52.60404@soft.uni-linz.ac.at>
Hi Rene,
> Unfortunately Acer does not seem to provide one, they don't even seem to
> support the BT-500 properly anymore. Thus I am now stuck with a hardware
> which does not seem to support what I intend to do - time to buy new
> hardware....
> Which USB Bluetooth adapters are currently recommended for Bluez ? With
> which do people have good experiences concerning stability ? It should
> support inquiry and L2CAP connections at the same time and (which I'll
> most probably need in the near future) BNEP/PAN. A RTFM-link would be
> wonderful, if there's a list of known-good devices and revisions up
> somewhere.
all CSR firmwares with HCI 16.x and greater are fine.
http://www.holtmann.org/linux/bluetooth/features.html
http://www.holtmann.org/linux/bluetooth/csr.html
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2003-10-13 9:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F86784F.9050608@soft.uni-linz.ac.at>
[not found] ` <1065778372.14923.336.camel@baroque.rococosoft.com>
[not found] ` <3F86A88E.4090106@soft.uni-linz.ac.at>
[not found] ` <1065790691.14513.173.camel@pegasus>
[not found] ` <3F86AF96.7000904@soft.uni-linz.ac.at>
[not found] ` <1065791594.14514.179.camel@pegasus>
2003-10-10 13:23 ` [Bluez-devel] Re: command tx timeout and continuous inquiry Rene Mayrhofer
2003-10-13 10:28 ` Rene Mayrhofer
2003-10-13 9:19 ` Marcel Holtmann [this message]
[not found] ` <3F8FB6D9.8030000@soft.uni-linz.ac.at>
[not found] ` <1066636708.902.5.camel@pegasus>
2003-10-21 10:45 ` Rene Mayrhofer
2003-10-21 11:32 ` Marcel Holtmann
2003-10-21 12:09 ` Rene Mayrhofer
2003-10-21 12:13 ` Marcel Holtmann
2003-10-21 13:04 ` Rene Mayrhofer
2003-10-21 14:31 ` [Bluez-devel] Stress testing (Was: Re: command tx timeout and continuous inquiry.) Rene Mayrhofer
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=1066036791.14513.186.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=rene@soft.uni-linz.ac.at \
/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