From: Imre Deak <imre.deak@nokia.com>
To: Bluez-Devel <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] L2CAP retransmission, flow control
Date: Wed, 09 Feb 2005 09:40:54 +0200 [thread overview]
Message-ID: <1107934854.9489.4.camel@mammoth.research.nokia.com> (raw)
Hi,
is anyone involved in implementing L2CAP rfc according to the 1.2 spec?
If not I'll give it a try.
Regards,
Imre
-------------------------------------------------------
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 reply other threads:[~2005-02-09 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 7:40 Imre Deak [this message]
2005-02-09 8:48 ` [Bluez-devel] L2CAP retransmission, flow control Marcel Holtmann
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=1107934854.9489.4.camel@mammoth.research.nokia.com \
--to=imre.deak@nokia.com \
--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