Hi Bastien,
On Fri, Apr 17, 2009, Bastien Nocera wrote:
On Fri, 2009-04-17 at 09:46 -0300, Luiz Augusto von Dentz wrote:
Hi,
On Thu, Apr 16, 2009 at 10:47 PM, Xu, Martin <martin.xu@xxxxxxxxx> wrote:
>>I know the way you mentioned, but this way has some issue. You know there is >a time interval between AdapterAdded and DeviceCreated.
> I found that the time interval on my machine is about 230 milliseconds. The time is enough to schedule out to other process to handle the AdapterAdded signal.
There is a fix for this race condition already on git, release 4.36
will be shipped with it. AdapterAdded is now emitted when adapter
properties are "ready", the problem was that we need the adapter
address for accessing the storage but that is only available when
receiving DEVUP event but we were actually emitting AdapterAdded
before when handling DEVREG event. The interval you mentioned is
probably the interval between DEVREG and DEVUP, with the fix it
shouldn't happen anymore since AdapterAdded will only be triggered by
the very first DEVUP to that device.
Does this mean I can remove the work-arounds in gnome-bluetooth, to
check for the "Powered" property change before enumerating the devices?
Yes, it should mean just that.
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
