From: Edd Dumbill <edd@usefulinc.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Re: [BlueZ-Announce] Release of bluez-libs-2.9 and bluez-utils-2.9
Date: Sun, 08 Aug 2004 17:12:01 +0100 [thread overview]
Message-ID: <1091981521.6281.39.camel@saag> (raw)
In-Reply-To: <1091123717.12651.107.camel@pegasus>
On Thu, 2004-07-29 at 19:55 +0200, Marcel Holtmann wrote:
> Hi Folks,
>
> I released a new stable version of the Bluetooth library and also the
> utilities. The library contains only small updates, but the utilities
> got some major enhancements in the HID area. The EPoX keyboards and
> their new HID presenters should now work correct in report protocol
> mode.
I just ploaded these to Debian unstable; they should be available in the
archive later today. I also updated the vastly out of date bluez-
hcidump.
> With this version the bluez-bluefw is deprecated by the bluez-firmware
> package. The Broadcom firmware loading utility for 2.4 kernels is now
> also part of the bluez-utils package and was renamed to bcm203x.
I have not yet enabled this in the Debian package as it will mean a new
package, which would have delayed the upload of 2.9. When I do enable
it, it will be in a package called bluez-bcm203x. Sometime in the next
two weeks I hope.
-- Edd
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
parent reply other threads:[~2004-08-08 16:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1091123717.12651.107.camel@pegasus>]
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=1091981521.6281.39.camel@saag \
--to=edd@usefulinc.com \
--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