From: Marcel Holtmann <marcel@holtmann.org>
To: Andreas Gaufer <andreas.gaufer@blue-cell-networks.com>
Cc: Bluez Devel <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hci_create_connection assuming timeout too soon
Date: Sat, 12 Jun 2004 11:45:16 +0200 [thread overview]
Message-ID: <1087033515.4306.0.camel@pegasus> (raw)
In-Reply-To: <20040609154824.531c71b8.Andreas.Gaufer@blue-cell-networks.com>
Hi Andreas,
> I noticed that many tools that use hci_create_connection use a hard coded
> timeout-value that varries between 1000 and 25000. 1000 is much to short for
> most mobile phones.
>
> This leads to error messages even if the chip didnt report a "connection
> complete" yet. Very often a conection complete with 00 is reported
> later but the tool did exit already.
>
> IMHO we could rely on the chips page timeout and wait for its "connection
> complete" event. This timeout can also be changed with hciconfig pageto
> by the user.
>
> To catch a condition where the chip is stalled in some way i think the best
> approach would be to time out on host side after the chips
> page time out * 1,5 or so.
>
> I changed hcitool to make it possible to specifiy the host side
> timeout via command line but i dont belive that this is a good aproach because
> it only fixes the symthoms not the root of the problem. Anyways I attach the
> patch against the latest CVS-HEAD to show what im talking about.
>
> In the moment my time is extremly short, i will try to bring up some code
> that realy helps here later. Since im not that familiar with C please let me
> know if somethings not right with my changes.
your change is me too much at the moment. I simply changed the timeout
to 25000 for the hcitool cc command.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-12 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 13:48 [Bluez-devel] hci_create_connection assuming timeout too soon Andreas Gaufer
2004-06-12 9:45 ` Marcel Holtmann [this message]
2004-06-14 13:24 ` Steven Singer
2004-06-14 16:23 ` Marcel Holtmann
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=1087033515.4306.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andreas.gaufer@blue-cell-networks.com \
--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