From: Marcel Holtmann <marcel@holtmann.org>
To: Thor Egil Skaug <paxtonrd@hotmail.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Broadcast and reassembly
Date: Fri, 05 Mar 2004 23:38:02 +0100 [thread overview]
Message-ID: <1078526281.19852.48.camel@pegasus> (raw)
In-Reply-To: <000101c402dd$9f3316d0$9349edc7@thores>
Hi Thor,
> I am experiencing some problems when reassembling active broadcast
> messages when the
> (hci) num_broadcast_retransmissions is set > 0 (at the sender), and with
> a decent L2CAP message size,
> > 100 bytes.
>
> I constantly get start_fragments and continuing_fragments that are out
> of order, and since
> the l2cap header is the only way I can know when I am done reading one
> message and can expect
> another, this is troublesome. I thought the device was supposed to
> deliver messages in order?
>
> Has anyone ever implemented this, and hopefully had the same
> experiences?
I never worked with any kind of broadcast and Bluetooth. Some people
tried this before, but nobody came up with a patch or something else.
This can be your job ;)
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-05 22:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 18:13 [Bluez-users] Broadcast and reassembly Thor Egil Skaug
2004-03-05 22:38 ` Marcel Holtmann [this message]
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=1078526281.19852.48.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=paxtonrd@hotmail.com \
/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