Re: L2CAP: One failing connection hurts others?

Hi Stefan,

> > > Your suggestions have no effect for me. Still errno 16. I think at the 
> > > moment it is not possible to connect concurrently via l2cap if one 
> > > device is down. But as a workaround I can use non-blocking connect (but 
> > > with a timeout of 60 seconds just to prevent deadlocks) and simply 
> > > reduce the pageto. My connection attempts are sequential anyway because 
> > > of the master-slave-limit. But I would suggest to change the behavior of 
> > > l2cap to allow more concurrent connection attempts even if some devices 
> > > are down.
> > >     
> > use hcidump and check the result code of the failing HCI connection
> > complete event. Look them up in the Bluetooth specification. This may
> > lights this behaviour a little bit more up.
> > 
> I guess you mean one paging process at one time per device? :)

there is always an underlaying creation of an ACL link and this fails
for you. The Bluetooth error codes don't map 1:1 to Unix error codes, so
use hcidump to find out the Bluetooth error and look up what it means.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php