From: Charles Bueche <charles@bueche.ch>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] BlueZ investigation
Date: Thu, 14 Apr 2005 22:20:10 +0200 [thread overview]
Message-ID: <1113510010.11953.13.camel@bluez.bueche.ch> (raw)
In-Reply-To: <425E9118.7040101@palmsource.com>
Hi Fred,
you would be wise to use bluez for at least the following 2 reasons :
- it's delivered with the stock kernel, so you won't depend on a vendor
for updates
- my T5 crashes too often while I do Bluetooth operations. Don't know
what you have been used until now in PalmOs, but Bluez is magnitudes
better in stability.
my 2ct worth.
Charles
On jeu, 2005-04-14 at 17:49 +0200, Frederic Danis wrote:
> Hi,
>
> In our move to Linux, we are investigating different Bluetooth stacks
> (proprietary or free).
> About BlueZ, I am asked about interoperability issues: do you know if
> there are companies attending the unplugged fests to test their
> BlueZ-based products? Do you have info about commercial devices
> interoperating with BlueZ?
> Please, send me any comments that can help me to decide my managment.
>
> Thanks!
>
> Fred
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2005-04-14 20:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-14 15:49 [Bluez-devel] BlueZ investigation Frederic Danis
2005-04-14 16:22 ` Marcel Holtmann
2005-04-14 20:20 ` Charles Bueche [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=1113510010.11953.13.camel@bluez.bueche.ch \
--to=charles@bueche.ch \
--cc=bluez-devel@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