From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP retransmission, flow control
Date: Wed, 09 Feb 2005 09:48:07 +0100 [thread overview]
Message-ID: <1107938887.13863.4.camel@pegasus> (raw)
In-Reply-To: <1107934854.9489.4.camel@mammoth.research.nokia.com>
Hi Imre,
> is anyone involved in implementing L2CAP rfc according to the 1.2 spec?
not that I know of.
> If not I'll give it a try.
Feel free to start. I am happy to get L2CAP 1.2 support included. The
L2CAP options now contain a mode value and this is exactly for this
purpose. Let the rest of the RFC config values be the defaults from the
specification by now. Another way to activate RFC would be to use the
SOCK_STREAM socket type.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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-02-09 8:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 7:40 [Bluez-devel] L2CAP retransmission, flow control Imre Deak
2005-02-09 8:48 ` Marcel Holtmann [this message]
2005-02-09 9:22 ` Imre Deak
2005-02-09 10:18 ` Marcel Holtmann
2005-02-09 13:24 ` Imre Deak
2005-02-09 14:06 ` Marcel Holtmann
2005-02-09 17:04 ` Imre Deak
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=1107938887.13863.4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.