From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Bluetooth kernel patch for 2.6.0
Date: Tue, 23 Dec 2003 01:26:05 +0100 [thread overview]
Message-ID: <1072139164.2876.39.camel@pegasus> (raw)
Hi Folks,
the first Bluetooth kernel patch for 2.6.0 is now available [1] and it
contains a bunch of updates to sync up with the Bluetooth subsystem of
the Linux 2.6 series. Here is the changelog:
o Add missing maintainer entries for the Bluetooth subsystem
o Add CAPI message transport protocol support
o Update the Kconfig entry for the BlueFRITZ! USB driver
o Add module aliases for the Bluetooth protocols
o Correct the module alias for the network family
o Support for AVM BlueFRITZ! USB
o Remove USB zero packet option
o Support inquiry results with RSSI
o Update HCI security filter
o Add support for an old ALPS module
o Add support for the Digianswer USB devices
o Always use two ISOC URB's
o Disable credit based flow control by default
Regards
Marcel
[1] http://www.holtmann.org/linux/kernel/patch-2.6.0-mh1.gz
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2003-12-23 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-23 0:26 Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-02 10:58 [Bluez-devel] Bluetooth kernel patch for 2.6.0 Marcel Holtmann
2004-01-02 14:04 ` Olivier Bornet
2004-01-02 23:40 ` Marcel Holtmann
2004-01-02 23:03 ` Edd Dumbill
2004-01-02 23:31 ` 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=1072139164.2876.39.camel@pegasus \
--to=marcel@holtmann.org \
--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