linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Till Harbaum <harbaum@beecon.de>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP dropping packets on BlueZ based receiver
Date: Tue, 3 Aug 2004 12:23:11 +0200	[thread overview]
Message-ID: <200408031223.11789.harbaum@beecon.de> (raw)
In-Reply-To: <1091472875.4259.6.camel@pegasus>

Hi Marcel,

On Monday 02 August 2004 20:57, Marcel Holtmann wrote:
> Some Bluetooth stacks emulate L2CAP flow control with the flow control
> of the HCI layer, but this is more bad than dropping a packet. Actually
> this is the reason why most mobiles phones don't support more than one
> ACL at the same time.
Hmm ... you are right. I have been implementing l2cap and have never really 
faced this problem. In fact i have been using HCI layer flow control to have 
a reliable L2CAP layer and thus, one blocking L2CAP client will affect all 
clients.

> The solution for this is using RFCOMM or L2CAP with retransmission and
> flow control from the Bluetooth 1.2 specification.
It's been some time since i wrote my rfcomm layer, but i didn't remember 
rfcomm having a sequence number or the like and IMHO it does not have a 
mechanism for retransmission. Or have i really missed something that 
important?

IMHO you can use rfcomm to make the whole transmission reliable, but this 
means, that you have to use acl flow control and make sure, that l2cap/acl 
won't block via rfcomms credit based flow control. Are there other options?

Thanks for your hints so far.

Till

-- 
Dr.-Ing. Till Harbaum                       Tel.:  +49 721 4998963
BeeCon GmbH                                 Fax:   +49 721 4998962
Haid-und-Neu Strasse 7, 76131 Karlsruhe     Mobil: +49 179 9087904
harbaum@beecon.de                           http://www.beecon.de


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-08-03 10:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02 16:59 [Bluez-devel] L2CAP dropping packets on BlueZ based receiver Till Harbaum
2004-08-02 18:57 ` Marcel Holtmann
2004-08-03 10:23   ` Till Harbaum [this message]
2004-08-03 11:24     ` Marcel Holtmann
2004-08-03 12:16       ` Till Harbaum
2004-08-03 13:09         ` Marcel Holtmann
2004-08-03 13:29           ` Till Harbaum
2004-08-03 13:45             ` Marcel Holtmann
2004-08-04 15:24               ` [Bluez-devel] Disconnection Time Out Talbi
2004-08-04 22:24                 ` David Woodhouse

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=200408031223.11789.harbaum@beecon.de \
    --to=harbaum@beecon.de \
    --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;
as well as URLs for NNTP newsgroup(s).