From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] hci connect and switch role modifications
Date: Thu, 29 Dec 2005 19:47:11 +0100 [thread overview]
Message-ID: <1135882032.5426.0.camel@localhost.localdomain> (raw)
In-Reply-To: <loom.20051229T161453-986@post.gmane.org>
Hi Marcello,
> we are working with Bluetooth and BlueZ since two years, and during the
> development of a field failure data analysis of Bluetooth networks, we
> experienced some annoying and frequent runtime errors that could be avoided.
> Those errors concern the creation of a L2CAP connection via HCI and the role
> switch operation. However, we discovered how to prevent these errors from
> occurring, by adding a little amount of code in the hci_create_connection and
> hci_switch_role functions in hci.c.
>
> We would like to contribute to the development and let the community know and
> evaluate these modifications.
>
> If you are interested, let us know what is the procedure to contribute.
simply sent a unified diff against the latest CVS to the mailing list.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-29 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-29 15:53 [Bluez-devel] hci connect and switch role modifications Marcello e Fabio
2005-12-29 18:47 ` Marcel Holtmann [this message]
2006-02-21 16:03 ` Capaianca
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=1135882032.5426.0.camel@localhost.localdomain \
--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;
as well as URLs for NNTP newsgroup(s).