From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] How to process fragmentation synchronously when two l2cap connections over one acl connection?
Date: Thu, 13 Apr 2006 19:18:20 +0200 [thread overview]
Message-ID: <1144948700.11159.53.camel@localhost> (raw)
In-Reply-To: <ef9938ec0604130949q67168579m85a3eb9521cdae91@mail.gmail.com>
Hi Albert,
> l2cap packets are always identified by a channel ID, which is
> negotiated when each l2cap connection (channel) is established.
> Continuation fragments always have the channel ID in the packet
> header, so there is no ambiguity over which continuation fragment
> belongs to which connection. You should take another look at the
> L2CAP section in the core spec.
you are not allowed to mix L2CAP fragments. As simple as that.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-04-13 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 5:33 [Bluez-devel] How to use hciemu to transfer files in Emulation environment Wang, Jing J
[not found] ` <OF01649481.41C9F474-ON4825714F.003F0EC5-4825714F.004171CE@zte.com.cn>
2006-04-13 16:49 ` [Bluez-devel] How to process fragmentation synchronously when two l2cap connections over one acl connection? Albert Huang
2006-04-13 17:18 ` Marcel Holtmann [this message]
2006-04-17 4:51 ` Mayank Batra
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=1144948700.11159.53.camel@localhost \
--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.