From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: Brian Gix <brian.gix@intel.com>
Subject: [PATCH 0/7] Bluetooth Mesh Daemon
Date: Wed, 25 Apr 2018 07:20:35 -0700 [thread overview]
Message-ID: <20180425142042.1262-1-brian.gix@intel.com> (raw)
This is our starting point for creating a stand-alone Mesh Daemon.
The Mesh Daemon (meshd) is intended to eventually co-exist beside the
Bluetooth Daemon (bluetoothd), and either daemon may exist without the
other. The Mesh Daemon will need full control/ownership of a
BT Controller that supports at least Core Spec revision 4.0 or
greater. It works strictly over the Advertising bearer, but we
have plans to extend it to support Mesh Proxy Server over GATT, at
which point it will require support from bluetoothd.
The current meshd, and it's companion Non-Background Command-line
version btmesh, exists fully within user-space, but requires an
HCI_USER socket to the kernel controler, and currently requires root
privledges.
This first revision is intended to operate as a standard
(non-provisioner) node. It includes the Configuration Server model,
and if it cannot find it's Mesh Configuration, will look for it's
Composition data, and start up as unprovisioned, and accept an
incoming PB-ADV provisioning session.
Two of us (Inga and Brian) have been working on this, and will be
the initial supporters and maintainers, and we gladly invite other
interested parties to participate.
Brian Gix (2):
meshd: Shared private meshd interfaces
meshd: Upper Transport on down Implementation
Inga Stotland (5):
meshd: Header files for mesh access layer and utilities
meshd: Source files for mesh access layer and utilities
meshd: Read and write mesh configuration in JSON format
meshd: Sample device composition in JSON fromat
Makefile for meshd and configure.ac
Makefile.am | 1 +
Makefile.meshd | 44 +
configure.ac | 2 +-
meshd/common/agent.c | 229 +++
meshd/common/agent.h | 42 +
meshd/common/mesh-defs.h | 84 +
meshd/common/util.c | 71 +
meshd/common/util.h | 25 +
meshd/config/composition.json | 44 +
meshd/mesh-json/mesh-db.c | 1360 +++++++++++++
meshd/mesh-json/mesh-db.h | 144 ++
meshd/src/appkey.c | 538 ++++++
meshd/src/appkey.h | 43 +
meshd/src/btmesh.c | 176 ++
meshd/src/cfgmod-server.c | 1194 ++++++++++++
meshd/src/cfgmod.h | 98 +
meshd/src/crypto.c | 1607 ++++++++++++++++
meshd/src/crypto.h | 164 ++
meshd/src/display.c | 67 +
meshd/src/display.h | 29 +
meshd/src/friend.c | 1116 +++++++++++
meshd/src/friend.h | 57 +
meshd/src/hci.c | 699 +++++++
meshd/src/hci.h | 56 +
meshd/src/main.c | 174 ++
meshd/src/mesh-io-api.h | 58 +
meshd/src/mesh-io-generic.c | 660 +++++++
meshd/src/mesh-io-generic.h | 20 +
meshd/src/mesh-io.c | 187 ++
meshd/src/mesh-io.h | 99 +
meshd/src/mesh.c | 184 ++
meshd/src/mesh.h | 32 +
meshd/src/model.c | 1274 +++++++++++++
meshd/src/model.h | 146 ++
meshd/src/net.c | 4188 +++++++++++++++++++++++++++++++++++++++++
meshd/src/net.h | 392 ++++
meshd/src/node.c | 851 +++++++++
meshd/src/node.h | 80 +
meshd/src/prov.c | 722 +++++++
meshd/src/prov.h | 162 ++
meshd/src/provision.c | 1159 ++++++++++++
meshd/src/provision.h | 30 +
meshd/src/storage.c | 673 +++++++
meshd/src/storage.h | 51 +
44 files changed, 19031 insertions(+), 1 deletion(-)
create mode 100644 Makefile.meshd
create mode 100644 meshd/common/agent.c
create mode 100644 meshd/common/agent.h
create mode 100644 meshd/common/mesh-defs.h
create mode 100644 meshd/common/util.c
create mode 100644 meshd/common/util.h
create mode 100644 meshd/config/composition.json
create mode 100644 meshd/mesh-json/mesh-db.c
create mode 100644 meshd/mesh-json/mesh-db.h
create mode 100644 meshd/src/appkey.c
create mode 100644 meshd/src/appkey.h
create mode 100644 meshd/src/btmesh.c
create mode 100644 meshd/src/cfgmod-server.c
create mode 100644 meshd/src/cfgmod.h
create mode 100644 meshd/src/crypto.c
create mode 100644 meshd/src/crypto.h
create mode 100644 meshd/src/display.c
create mode 100644 meshd/src/display.h
create mode 100644 meshd/src/friend.c
create mode 100644 meshd/src/friend.h
create mode 100644 meshd/src/hci.c
create mode 100644 meshd/src/hci.h
create mode 100644 meshd/src/main.c
create mode 100644 meshd/src/mesh-io-api.h
create mode 100644 meshd/src/mesh-io-generic.c
create mode 100644 meshd/src/mesh-io-generic.h
create mode 100644 meshd/src/mesh-io.c
create mode 100644 meshd/src/mesh-io.h
create mode 100644 meshd/src/mesh.c
create mode 100644 meshd/src/mesh.h
create mode 100644 meshd/src/model.c
create mode 100644 meshd/src/model.h
create mode 100644 meshd/src/net.c
create mode 100644 meshd/src/net.h
create mode 100644 meshd/src/node.c
create mode 100644 meshd/src/node.h
create mode 100644 meshd/src/prov.c
create mode 100644 meshd/src/prov.h
create mode 100644 meshd/src/provision.c
create mode 100644 meshd/src/provision.h
create mode 100644 meshd/src/storage.c
create mode 100644 meshd/src/storage.h
--
2.14.3
next reply other threads:[~2018-04-25 14:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 14:20 Brian Gix [this message]
2018-04-25 14:20 ` [PATCH 1/7] meshd: Shared private meshd interfaces Brian Gix
2018-04-25 14:20 ` [PATCH 3/7] meshd: Header files for mesh access layer and utilities Brian Gix
2018-04-25 14:20 ` [PATCH 5/7] meshd: Read and write mesh configuration in JSON format Brian Gix
2018-04-25 14:20 ` [PATCH 6/7] meshd: Sample device composition in JSON fromat Brian Gix
2018-04-25 14:20 ` [PATCH 7/7] Makefile for meshd and configure.ac Brian Gix
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=20180425142042.1262-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--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).