From: Arman Uguray <armansito@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Arman Uguray <armansito@chromium.org>
Subject: [PATCH BlueZ 0/2] core: device: GATT fixes
Date: Fri, 16 Jan 2015 19:26:29 -0800 [thread overview]
Message-ID: <1421465191-1494-1-git-send-email-armansito@chromium.org> (raw)
This patch fixes the following:
1. Bugs in GATT service browsing code-path that caused GAttrib-based
profiles to not work and caused D-Bus calls to "Pair" and/or "Connect"
to hang.
2. Reintroduced invalid service removal. This patch is the similar as
the one I submitted previously: it splits the UUID list into SDP and
GATT based lists and introduces new storage entries, except this patch
also includes a very simple migration mechanism from the existing
storage format to the new one.
The migration works by loading the UUIDs from the "Services" field and
delaying profile probing until connection establishment. Once a
connection is established and service discovery is performed, we
simply store the UUIDs in their new grouping and probe the profiles
and remove the previous entries. The legacy entries act as temporary
data that's fed into the Device1.UUIDs property but everything else
acts as if no services were discovered until connection.
Arman Uguray (2):
core: device: Fix bug in device_browse_gatt
core: device: Fix broken GATT UUID management
plugins/sixaxis.c | 2 +-
src/adapter.c | 8 +-
src/device.c | 410 +++++++++++++++++++++++++++++++++++++++---------------
src/device.h | 6 +-
4 files changed, 307 insertions(+), 119 deletions(-)
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2015-01-17 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-17 3:26 Arman Uguray [this message]
2015-01-17 3:26 ` [PATCH BlueZ 1/2] core: device: Fix bug in device_browse_gatt Arman Uguray
2015-01-17 3:26 ` [PATCH BlueZ 2/2] core: device: Fix broken GATT UUID management Arman Uguray
2015-01-20 20:16 ` [PATCH BlueZ 0/2] core: device: GATT fixes Arman Uguray
2015-01-21 20:28 ` Luiz Augusto von Dentz
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=1421465191-1494-1-git-send-email-armansito@chromium.org \
--to=armansito@chromium.org \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).