Re: [Bluez-devel] Re: command tx timeout and continuous inquiry.

[Marcel Holtmann <marcel@holtmann.org>]

Hi Rene,

> On my system, I can not confirm this. When I start two l2ping runs, 
> "hcitool scan" will never return a result (I have tried a number of 
> times). The interesting thing is the following: One l2ping runs in the 
> background and I start "hcitool scan". It will take 10 - 24 seconds and 
> will only return those devices which are currently _not_ pinged. When I 
> start the second l2ping when "hcitool scan" is still running, either:
> a) hcitool scan will immediately return (in less than 10 seconds) and 
> the l2ping will work
> b) hcitool scan will return with "Can't connect.: Device or ressource busy"
> I've not found a way to reliably reproduce on of the two, it seems to be 
> random which one will happen.

it is ok that devices with active connections don't answer inquiry scans
and you need to use --flush with hcitool to disable the kernel side
inquiry cache.

> PS: Is libbluetooth thread-safe ? Maybe that could be part of my problem 
> with two l2ping sessions from two different threads in the same process ?

I don't see any problems here, because you only use socket programming.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by OSDN developer relations
Here's your chance to show off your extensive product knowledge
We want to know what you know. Tell us and you have a chance to win $100
http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel