From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Brian Gix <brian.gix@intel.com>,
marcel@holtmann.org, luiz.dentz@gmail.com
Subject: [PATCH 1/5] mesh: Add BT SIG reserved numbers for Mesh
Date: Mon, 14 Aug 2017 12:01:15 -0700 [thread overview]
Message-ID: <20170814190119.8684-2-brian.gix@intel.com> (raw)
In-Reply-To: <20170814190119.8684-1-brian.gix@intel.com>
---
lib/uuid.h | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/lib/uuid.h b/lib/uuid.h
index 2dcfe9e..2c57a33 100644
--- a/lib/uuid.h
+++ b/lib/uuid.h
@@ -139,6 +139,16 @@ extern "C" {
#define GATT_EXTERNAL_REPORT_REFERENCE 0x2907
#define GATT_REPORT_REFERENCE 0x2908
+/* GATT Mesh Services */
+#define MESH_PROV_SVC_UUID "00001827-0000-1000-8000-00805f9b34fb"
+#define MESH_PROXY_SVC_UUID "00001828-0000-1000-8000-00805f9b34fb"
+
+/* GATT Mesh Characteristic Types */
+#define MESH_PROVISIONING_DATA_IN 0x2ADB
+#define MESH_PROVISIONING_DATA_OUT 0x2ADC
+#define MESH_PROXY_DATA_IN 0x2ADD
+#define MESH_PROXY_DATA_OUT 0x2ADE
+
typedef struct {
enum {
BT_UUID_UNSPEC = 0,
--
2.9.5
next prev parent reply other threads:[~2017-08-14 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 19:01 [PATCH 0/5] MeshCtl - Mesh GATT Client Provisioner Brian Gix
2017-08-14 19:01 ` Brian Gix [this message]
2017-08-14 19:01 ` [PATCH 2/5] mesh: define APIs for Bluetooth Mesh Brian Gix
2017-08-14 19:01 ` [PATCH 3/5] mesh: Baseline Mesh runtime configuration files Brian Gix
2017-08-14 19:01 ` [PATCH 4/5] mesh: Baseline Mesh implementation Brian Gix
2017-08-15 9:07 ` Luiz Augusto von Dentz
2017-08-15 15:36 ` Gix, Brian
2017-08-16 12:29 ` Luiz Augusto von Dentz
2017-08-14 19:01 ` [PATCH 5/5] mesh: Add mesh to main bluez build Brian Gix
2017-08-16 12:28 ` [PATCH 0/5] MeshCtl - Mesh GATT Client Provisioner Szymon Janc
2017-08-16 12:30 ` Luiz Augusto von Dentz
2017-08-21 10:42 ` Marcel Holtmann
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=20170814190119.8684-2-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--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