public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Stefan Mischke <survivor@uni-paderborn.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] L2CAP: One failing connection hurts others?
Date: Wed, 15 Sep 2004 09:46:16 +0200	[thread overview]
Message-ID: <1095234376.5263.10.camel@pegasus> (raw)
In-Reply-To: <414780B0.2070908@uni-paderborn.de>

Hi Stefan,

> > > Is there a way to upgrade it? Are there better dongles the University
> > > could buy?
> > >     
> > You can upgrade the D-Link DBT-120 Rev. B3 with the Apple firmware
> > update package to HCI 18.1.
> > 
> Would that solve the problem? Actually, is it a known problem?

only if there was a bug in previous CSR firmwares, but on the other hand
the HCI 18.x firmwares are Bluetooth 1.2 capable.

> Btw, I read something about getting RSSI via Inquiry. Is it possible
> with BlueZ? This could be used to faster decrease the backoff if the
> unavailable device is found by inquiry and probably with a good RSSI
> near 0.

You need a CSR dongle with HCI 18.x firmware, a newer Silicon Wave or
the AVM BlueFRITZ! USB v2.0 to use inquiry with RSSI. The support is
already included in BlueZ.

> > > One year ago, I wrote another Location Awareness App on top of a
> > > modified JBlueZ and it just used ACL links to measure RSSI and LQ. It
> > > worked. I probably have to take care of the ACLs myself (does L2CAP
> > > use existing ACLs?). The only drawback: The App has to run as root :(.
> > >     
> > The L2CAP creates the same ACL links, so this can't be the problem.
> > 
> Yes, but I could disconnect faster on timeout and make L2CAP throw a
> clean error instead of behaving strange. 
> 
> Connections:
>         < ACL 00:02:72:B1:1D:62 handle 0 state 5 lm MASTER
>         < ACL 00:02:72:B1:1D:6C handle 45 state 1 lm MASTER
> 
> stargazer:~ # hcitool dc 00:02:72:B1:1D:62
> Disconnect failed: Input/output error
> 
> The connection to 62 persists even 5 minutes after I pulled the 62
> Dongle out. A manual disconnect failed. This simply can't be! I
> sometimes even have to reboot because BlueZ or something is confused.
> I think there is a serious problem. I'll do further testing tomorrow.

There are more than one timeouts in the BlueZ stack. Even the ACL
disconnect timeout is different for the initiator and the acceptor of
and ACL connection. Keep an eye on the HCI disconnect events on each of
your devices and compare the timestamps.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-09-15  7:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 15:20 [Bluez-devel] L2CAP: One failing connection hurts others? Stefan Mischke
2004-09-14 18:34 ` Marcel Holtmann
2004-09-14 19:11   ` Stefan Mischke
2004-09-14 19:24     ` Marcel Holtmann
2004-09-14 19:37       ` Stefan Mischke
2004-09-14 19:49         ` Marcel Holtmann
2004-09-14 20:10           ` Stefan Mischke
2004-09-14 21:12             ` Marcel Holtmann
2004-09-14 23:37               ` Stefan Mischke
2004-09-15  7:46                 ` Marcel Holtmann [this message]
2004-09-15 14:00                   ` Stefan Mischke
2004-09-15 21:09                     ` Marcel Holtmann
2004-09-15 22:26                       ` Stefan Mischke
2004-09-16 10:30                       ` Stefan Mischke
2004-09-16 10:34                         ` Marcel Holtmann
2004-09-16 10:39                           ` Stefan Mischke
2004-09-16 11:00                             ` Marcel Holtmann
2004-09-16 11:10                               ` Stefan Mischke
2004-09-16 16:41                               ` Stefan Mischke
2004-09-15 20:37                   ` Stefan Mischke
2004-09-15 21:06                     ` Marcel Holtmann
2004-09-15 22:13                       ` Stefan Mischke

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=1095234376.5263.10.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=survivor@uni-paderborn.de \
    /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