Linux bluetooth development
 help / color / mirror / Atom feed
* [Bluez-users] Broadcast and reassembly
@ 2004-03-05 18:13 Thor Egil Skaug
  2004-03-05 22:38 ` Marcel Holtmann
  0 siblings, 1 reply; 2+ messages in thread
From: Thor Egil Skaug @ 2004-03-05 18:13 UTC (permalink / raw)
  To: bluez-users

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?

Thanks,

Thor


-------------------------------------------------------
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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Bluez-users] Broadcast and reassembly
  2004-03-05 18:13 [Bluez-users] Broadcast and reassembly Thor Egil Skaug
@ 2004-03-05 22:38 ` Marcel Holtmann
  0 siblings, 0 replies; 2+ messages in thread
From: Marcel Holtmann @ 2004-03-05 22:38 UTC (permalink / raw)
  To: Thor Egil Skaug; +Cc: BlueZ Mailing List

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-05 22:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-05 18:13 [Bluez-users] Broadcast and reassembly Thor Egil Skaug
2004-03-05 22:38 ` Marcel Holtmann

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox