From: Adam Lee <adam8157@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] core: retry connect_dbus() several times
Date: Fri, 28 Feb 2014 15:31:13 +0800 [thread overview]
Message-ID: <20140228073113.GA3771@adam-laptop> (raw)
In-Reply-To: <04802ECE-6B8D-4DF4-BFFD-EABBD42BD30F@holtmann.org>
On Thu, Feb 27, 2014 at 11:15:01PM -0800, Marcel Holtmann wrote:
> Hi Adadm,
>
> > Sometimes the hardware, especially which needs firmware patching, is not
> > yet ready when connect_dbus().
>
> this makes no sense. Connecting to D-Bus has nothing to do with
> firmware patching. What are you exactly fixing here?
connect_dbus() fails sometimes with Intel 7260 bluetooth, sleeping 0.5s
before executing bluetoothd workarounds it. I assume the firmware
patching slows down hardware initialization then fails to connect.
Any other possibility? I'm not a D-Bus guru :)
--
Adam Lee
http://adam8157.info
next prev parent reply other threads:[~2014-02-28 7:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 7:09 [PATCH BlueZ] core: retry connect_dbus() several times Adam Lee
2014-02-28 7:15 ` Marcel Holtmann
2014-02-28 7:31 ` Adam Lee [this message]
2014-02-28 7:40 ` Marcel Holtmann
2014-02-28 12:22 ` Anderson Lizardo
2014-02-28 14:10 ` Luiz Augusto von Dentz
2014-03-03 7:15 ` Adam Lee
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=20140228073113.GA3771@adam-laptop \
--to=adam8157@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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