From: Johan Hedberg <johan.hedberg@nokia.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
connman@moblin.org, "Yin, Kangkai" <kangkai.yin@intel.com>,
"linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
"Liu, Bing Wei" <bing.wei.liu@intel.com>,
"Gao, Bin" <bin.gao@intel.com>
Subject: Re: [connman] CreatDevice signal should be emitted at function create_stored_device_from_profiles() in src/adapter.c
Date: Fri, 17 Apr 2009 16:08:48 +0300 [thread overview]
Message-ID: <20090417130848.GA11008@localhost> (raw)
In-Reply-To: <1239973488.9313.3017.camel@cookie.hadess.net>
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@intel.com> 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
next prev parent reply other threads:[~2009-04-17 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-31 11:29 PAN with bluez-utils-3 Florian Philipp
2009-03-31 13:44 ` Luiz Augusto von Dentz
2009-04-01 6:55 ` Florian Philipp
2009-04-02 6:02 ` Florian Philipp
2009-04-02 17:28 ` Luiz Augusto von Dentz
2009-04-15 14:44 ` Florian Philipp
2009-04-16 8:49 ` CreatDevice signal should be emitted at function create_stored_device_from_profiles() in src/adapter.c Xu, Martin
2009-04-16 13:31 ` [connman] " Luiz Augusto von Dentz
2009-04-17 0:43 ` Xu, Martin
2009-04-17 1:47 ` Xu, Martin
2009-04-17 12:46 ` Luiz Augusto von Dentz
2009-04-17 13:04 ` Bastien Nocera
2009-04-17 13:08 ` Johan Hedberg [this message]
2009-04-20 0:57 ` Xu, Martin
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=20090417130848.GA11008@localhost \
--to=johan.hedberg@nokia.com \
--cc=bin.gao@intel.com \
--cc=bing.wei.liu@intel.com \
--cc=connman@moblin.org \
--cc=hadess@hadess.net \
--cc=kangkai.yin@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
/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