From: Marcel Holtmann <marcel@holtmann.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Questions about BlueZ in commercial use
Date: Sun, 27 Jun 2004 21:09:57 +0200 [thread overview]
Message-ID: <1088363397.3774.64.camel@pegasus> (raw)
In-Reply-To: <20040627191016.GA26191@gmx.net>
Hi Nicholas,
> > That is wrong. BlueZ itself is stable. Speaking about the kernel part
> > then every code in a stable kernel like 2.4 and 2.6 is stable. Bugs
> > exists and later kernel releases are more stable than previous, but
> > every BlueZ code in the kernel can be considered as stable.
>
> I wouldn't consider 2.6. as stable. And i think it is not recommend to
> use anything related to USB with 2.6. in a commercial standalone device.
the Linux kernel 2.6 itself first will become mature if Andrew takes
over the maintainer role and the 2.7 branch is created. However the
kernel itself is stable and the BlueZ core is also stable. The USB
problem you are talking about is a driver problem (hci_usb) only and
don't effect the BlueZ core.
This is a another nice point why I don't really wanna start thinking in
black/white or stable/testing categories. Choose what you need and then
you can start talking about how stable this will be for a specific use
case.
Regards
Marcel
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-27 19:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 9:47 [Bluez-devel] Questions about BlueZ in commercial use KeiHachi
2004-06-27 12:52 ` Nicholas A. Preyss
2004-06-27 14:45 ` KeiHachi
2004-06-27 17:13 ` Nicholas A. Preyss
2004-06-28 16:30 ` KeiHachi
2004-06-28 17:22 ` Marcel Holtmann
2004-06-27 18:29 ` Marcel Holtmann
2004-06-28 16:33 ` KeiHachi
2004-06-28 17:45 ` Marcel Holtmann
2004-06-28 14:39 ` Ademar de Souza Reis Jr.
2004-06-28 14:48 ` Marcel Holtmann
2004-06-28 15:19 ` Ademar de Souza Reis Jr.
2004-06-28 15:38 ` Marcel Holtmann
2004-06-28 15:59 ` Stephen Crane
2004-06-28 17:06 ` Ademar de Souza Reis Jr.
2004-06-28 17:15 ` Marcel Holtmann
2004-06-27 18:09 ` Marcel Holtmann
2004-06-27 19:10 ` Nicholas A. Preyss
2004-06-27 19:09 ` Marcel Holtmann [this message]
2004-06-27 20:34 ` Nicholas A. Preyss
2004-06-27 20:49 ` Marcel Holtmann
2004-06-27 21:42 ` Nicholas A. Preyss
2004-06-28 7:37 ` Marcel Holtmann
2004-06-28 16:28 ` KeiHachi
2004-06-28 17:13 ` Marcel Holtmann
2004-06-29 17:08 ` KeiHachi
2004-06-29 17:41 ` Marcel Holtmann
2004-06-30 16:22 ` KeiHachi
2004-06-30 18:11 ` Marcel Holtmann
2004-07-04 8:57 ` KeiHachi
2004-07-04 11:38 ` Marcel Holtmann
2004-07-04 13:19 ` Peter Favrholdt
2004-07-04 13:47 ` Marcel Holtmann
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=1088363397.3774.64.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=nalp@gmx.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