Re: [Bluez-devel] hci_create_connection assuming timeout too soon

[Marcel Holtmann <marcel@holtmann.org>]

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