From: Stephen Crane <steve.crane@rococosoft.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>,
Max Krasnyansky <maxk@qualcomm.com>,
Edd Dumbill <edd@usefulinc.com>
Subject: Re: Release of new BlueZ libs and utils
Date: 19 Dec 2003 10:15:06 +0000 [thread overview]
Message-ID: <1071828905.26243.613.camel@baroque.rococosoft.com> (raw)
In-Reply-To: <1071791711.6635.18.camel@pegasus>
Hi Marcel,
The corresponding RPM packages are now there too.
Cheers,
Steve
On Thu, 2003-12-18 at 23:55, Marcel Holtmann wrote:
> Hi Folks,
>
> I don't wanna make big words about it, but after 8 months there are new
> releases of the BlueZ libs and utils packages. So let the changelogs
> speak for themselfs:
>
> BlueZ libs 2.5:
> Add decoding of Bluetooth 1.2 features.
> Add link manager version parameter for Bluetooth 1.2.
> Add new company identifiers.
> Support for transmit power level.
> Support for park, sniff and hold mode.
> Support for role switch.
> Support for reading the clock offset.
> Use R1 for default value of pscan_rep_mode.
>
> BlueZ utils 2.4:
> hcitool changes:
> Increase number of inquiry responses.
> Support for transmit power level.
> Minor updates.
> hciconfig changes:
> Display all 8 bytes of the features.
> Add support for reading and writing of IAC.
> Correct decoding class of device.
> Use Ericsson revision command for ST Microelectronics devices.
> Display AVM firmware version with 'revision' command.
> New code for CSR specific revision information.
> hciattach changes:
> Support for ST Microelectronics specific initialization.
> Support for 3Com card version 3.0.
> Support for TDK, IBM and Socket cards.
> Support for initial baud rate.
> Update man pages.
> Fixes for some memory leaks.
>
> For the BlueZ libs I don't plan another release, because the new major
> version of the Bluetooth library is making good progress. But for the
> BlueZ Utils I want to make another release that addresses the problems
> with the pin_helper program. I think the C based bluez-pin is a good
> idea and maybe we should also integrate the DBus support into the next
> release. So I like to get comments on this and if you have patches,
> please resend them.
>
> Regards
>
> Marcel
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
steve.crane@rococosoft.com +353-1-6601315 (ext 209)
next prev parent reply other threads:[~2003-12-19 10:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 23:55 [Bluez-users] Release of new BlueZ libs and utils Marcel Holtmann
2003-12-19 0:28 ` Michal Semler (volny.cz)
2003-12-19 9:19 ` Marcel Holtmann
2003-12-19 10:22 ` Michal Semler (volny.cz)
2003-12-20 7:14 ` Charles Bueche
2003-12-20 14:39 ` Marcel Holtmann
2003-12-19 10:15 ` Stephen Crane [this message]
2004-01-01 20:39 ` Edd Dumbill
2004-01-02 11:04 ` [Bluez-users] " Marcel Holtmann
2004-01-02 11:09 ` Edd Dumbill
2004-01-02 11:24 ` [Bluez-users] " Marcel Holtmann
2004-01-02 17:18 ` Michal Semler (volny.cz)
2004-01-02 23:35 ` Marcel Holtmann
2004-01-03 19:54 ` Michal Semler (volny.cz)
2004-01-04 10:35 ` Marcel Holtmann
2004-01-03 16:32 ` [Bluez-users] " Edd Dumbill
2004-01-03 16:47 ` Edd Dumbill
2004-01-03 17:10 ` Marcel Holtmann
2004-01-03 18:33 ` Edd Dumbill
2004-01-04 10:38 ` Marcel Holtmann
2004-01-06 11:26 ` Edd Dumbill
2004-01-06 12:37 ` Marcel Holtmann
2004-01-06 13:11 ` Edd Dumbill
2004-01-06 13:20 ` Marcel Holtmann
2004-01-06 14:02 ` Edd Dumbill
2004-01-06 14:15 ` Marcel Holtmann
2004-01-06 14:30 ` Edd Dumbill
2004-01-06 14:18 ` Xavier Garreau
2004-01-06 12:54 ` Xavier Garreau
2004-01-06 13:06 ` 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=1071828905.26243.613.camel@baroque.rococosoft.com \
--to=steve.crane@rococosoft.com \
--cc=bluez-users@lists.sourceforge.net \
--cc=edd@usefulinc.com \
--cc=marcel@holtmann.org \
--cc=maxk@qualcomm.com \
/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