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 3/5] mesh: Baseline Mesh runtime configuration files
Date: Mon, 14 Aug 2017 12:01:17 -0700 [thread overview]
Message-ID: <20170814190119.8684-4-brian.gix@intel.com> (raw)
In-Reply-To: <20170814190119.8684-1-brian.gix@intel.com>
---
mesh/local_node.json | 61 ++++++++++++++++++++++++++++++++++++++++++++++++++++
mesh/prov_db.json | 37 +++++++++++++++++++++++++++++++
2 files changed, 98 insertions(+)
create mode 100644 mesh/local_node.json
create mode 100644 mesh/prov_db.json
diff --git a/mesh/local_node.json b/mesh/local_node.json
new file mode 100644
index 0000000..6591289
--- /dev/null
+++ b/mesh/local_node.json
@@ -0,0 +1,61 @@
+{
+ "$schema":"file:\/\/\/Bluetooth SIG\/Mesh\/schema\/mesh.jsonschema",
+ "meshName":"Intel BT Mesh",
+ "netKeys":[
+ {
+ "index": 0,
+ "keyRefresh": 0
+ }
+ ],
+ "appKeys":[
+ {
+ "index": 0,
+ "boundNetKey": 0
+ },
+ {
+ "index": 1,
+ "boundNetKey": 0
+ }
+ ],
+"node": {
+ "IVindex":"00000005",
+ "IVupdate":"0",
+ "sequenceNumber": 0,
+ "composition": {
+ "cid": "0002",
+ "pid": "0010",
+ "vid": "0001",
+ "crpl": "000a",
+ "features": {
+ "relay": false,
+ "proxy": true,
+ "friend": false,
+ "lowPower": false
+ },
+ "elements": [
+ {
+ "elementIndex": 0,
+ "location": "0001",
+ "models": ["0000", "0001", "1001"]
+ }
+ ]
+ },
+ "configuration":{
+ "netKeys": [0],
+ "appKeys": [ 0, 1],
+ "defaultTTL": 10,
+ "elements": [
+ {
+ "elementIndex": 0,
+ "unicastAddress":"0077",
+ "models": [
+ {
+ "modelId": "1001",
+ "bind": [1]
+ }
+ ]
+ }
+ ]
+ }
+ }
+}
diff --git a/mesh/prov_db.json b/mesh/prov_db.json
new file mode 100644
index 0000000..d810a7d
--- /dev/null
+++ b/mesh/prov_db.json
@@ -0,0 +1,37 @@
+{
+ "$schema":"file:\/\/\/Bluetooth SIG\/Mesh\/schema\/mesh.jsonschema",
+ "meshName":"Intel BT Mesh",
+ "IVindex":5,
+ "IVupdate":0,
+ "netKeys":[
+ {
+ "index":0,
+ "keyRefresh":0,
+ "key":"18eed9c2a56add85049ffc3c59ad0e12"
+ }
+ ],
+ "appKeys":[
+ {
+ "index":0,
+ "boundNetKey":0,
+ "key":"4f68ad85d9f48ac8589df665b6b49b8a"
+ },
+ {
+ "index":1,
+ "boundNetKey":0,
+ "key":"2aa2a6ded5a0798ceab5787ca3ae39fc"
+ }
+ ],
+ "provisioners":[
+ {
+ "provisionerName":"BT Mesh Provisioner",
+ "unicastAddress":"0077",
+ "allocatedUnicastRange":[
+ {
+ "lowAddress":"0100",
+ "highAddress":"7fff"
+ }
+ ]
+ }
+ ],
+}
--
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 ` [PATCH 1/5] mesh: Add BT SIG reserved numbers for Mesh Brian Gix
2017-08-14 19:01 ` [PATCH 2/5] mesh: define APIs for Bluetooth Mesh Brian Gix
2017-08-14 19:01 ` Brian Gix [this message]
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-4-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