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

Hi Marcel!

Marcel Holtmann schrieb:

>
>this is supported much longer, but it was not easy to get it working.
>
>  
>
Well, yes, I remember there was a device hci0, but it didn't work. I 
haven't tried any harder. Now (Kernel 2.6.5) it works just by pluggin it 
in as ist should. Nice, now I have 4 dongles but I need to assemble 
another pc from the parts lying around here...

>
>You must recompile your kernel and actually modifying them makes not
>really sense, because for example the HCI disconnect timeout is useful
>to keep the ACL link open for 2-4 seconds so that it can be reused by
>the next L2CAP connection.
>
>  
>
I fond something much easier and better: "hciconfig hci0 pageto 
<slots>". When I use connect() in blocking mode and set the pageto to a 
small value, the connection attempt failure is reported in acceptable 
time. Since hcitool can do it programmatically, I can surely do it, too 
(by simply looking it up). I noticed that I have to increase the pageto 
up to 10000 or higher for the first paging. I suppose because the clock 
offset needs to be synchronized and afterwards it work even with a 
pageto of only 1 slot (but 500 slots = 312,5 ms is ok for me).

Regards
Stefan

      reply	other threads:[~2004-09-15 22:13 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
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 [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=4148BE6F.4060802@uni-paderborn.de \
    --to=survivor@uni-paderborn.de \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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