From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: johan.hedberg@gmail.com, inga.stotland@intel.com,
marcel@holtmann.org, brian.gix@intel.com
Subject: [PATCH BlueZ v5 00/30] Major rewrite for Multi-Node and DBus
Date: Tue, 18 Dec 2018 20:19:46 -0800 [thread overview]
Message-ID: <20181219042016.25538-1-brian.gix@intel.com> (raw)
The Mesh Daemon has been largely rewritten.
It matches the API in doc/mesh-api.txt, and is now accessible
from non-privledged DBus clients. The commandline version has
been temporarily removed, although it will probably be re-added
in the future. The dBus privledges need to be adjusted to allow
for non-privledged access to Daemon interfaces. We will shortly
also be adding a Mesh Specific README and TODO file, but in
the meantime, contact Brian and/or Inga with any questions.
v5 -- Address Marcel's v4 comments.
Brian Gix (12):
mesh: Staging for Mesh DBus API rewrite
mesh: Delete obsolete files
mesh: Rewrite Network layer for multiple nodes
mesh: Direction agnostic PB-Adv implementation
mesh: Acceptor side provisioning implementation
mesh: Initiator side provisioning implementation
mesh: Rewrite Controler interface for full init
mesh: Unchanged variables set to const
mesh: re-arrange provisioning for DBus API
mesh: restructure I/O for multiple nodes
mesh: Clean-up Comment style
mesh: Enable building Mesh Daemon
Inga Stotland (18):
mesh: Utilities for DBus support
mesh: Internal errors
mesh: Rewrite storage for Multiple Nodes
mesh: Rewrite Node handling for multiple nodes
mesh: centralize generic utilities
mesh: Re-architect for DBus API
mesh: Make config model handle multiple nodes
mesh: Multi node Config Server model
mesh: Restructure DB to support multiple nodes
mesh: restructure model services for multiple nodes
mesh: DBUS interface for Provisioning Agent
mesh: restructure App Key storage
mesh: Update for DBus API and multi-node support
mesh: Add default location for Mesh Node storage
mesh: Add structural changes for mesh
mesh: Sample Provisioning Agent
mesh: Sample On/Off Client and Server
mesh: Sample Mesh Joiner (provision acceptor)
.gitignore | 1 -
Makefile.mesh | 19 +-
configure.ac | 3 +
mesh/agent.c | 664 +++++++++++++++++----
mesh/agent.h | 68 ++-
mesh/agent.py | 40 ++
mesh/appkey.c | 17 +-
mesh/btmesh.c | 181 ------
mesh/cfgmod-server.c | 173 +++---
mesh/cfgmod.h | 2 +-
mesh/config/composition.json | 44 --
mesh/dbus.c | 151 +++++
mesh/dbus.h | 34 ++
mesh/display.c | 64 --
mesh/error.h | 35 ++
mesh/example-onoff-client | 288 +++++++++
mesh/example-onoff-server | 365 ++++++++++++
mesh/friend.c | 76 +--
mesh/main.c | 73 ++-
mesh/mesh-db.c | 454 +++++++++-----
mesh/mesh-db.h | 6 +-
mesh/mesh-io-api.h | 2 +-
mesh/mesh-io-generic.c | 149 ++++-
mesh/mesh-io.c | 3 +-
mesh/mesh-io.h | 3 +-
mesh/mesh.c | 624 +++++++++++++++-----
mesh/mesh.h | 27 +-
mesh/model.c | 811 +++++++++++++++++--------
mesh/model.h | 66 ++-
mesh/net.c | 293 +++------
mesh/net.h | 31 +-
mesh/node.c | 1338 +++++++++++++++++++++++++++++++++++-------
mesh/node.h | 42 +-
mesh/pb-adv.c | 444 ++++++++++++++
mesh/{display.h => pb-adv.h} | 13 +-
mesh/prov-acceptor.c | 684 +++++++++++++++++++++
mesh/prov-initiator.c | 641 ++++++++++++++++++++
mesh/prov.c | 722 -----------------------
mesh/prov.h | 14 +-
mesh/provision.c | 1162 ------------------------------------
mesh/provision.h | 112 +++-
mesh/storage.c | 570 ++++++++----------
mesh/storage.h | 39 +-
mesh/test-join | 408 +++++++++++++
mesh/util.c | 26 +
mesh/util.h | 1 +
46 files changed, 7096 insertions(+), 3887 deletions(-)
create mode 100755 mesh/agent.py
delete mode 100644 mesh/btmesh.c
delete mode 100644 mesh/config/composition.json
create mode 100644 mesh/dbus.c
create mode 100644 mesh/dbus.h
delete mode 100644 mesh/display.c
create mode 100644 mesh/error.h
create mode 100644 mesh/example-onoff-client
create mode 100644 mesh/example-onoff-server
create mode 100644 mesh/pb-adv.c
rename mesh/{display.h => pb-adv.h} (71%)
create mode 100644 mesh/prov-acceptor.c
create mode 100644 mesh/prov-initiator.c
delete mode 100644 mesh/prov.c
delete mode 100644 mesh/provision.c
create mode 100644 mesh/test-join
--
2.14.5
next reply other threads:[~2018-12-19 4:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 4:19 Brian Gix [this message]
2018-12-19 4:19 ` [PATCH BlueZ v5 01/30] mesh: Staging for Mesh DBus API rewrite Brian Gix
2018-12-24 20:56 ` Marcel Holtmann
2018-12-19 4:19 ` [PATCH BlueZ v5 02/30] mesh: Delete obsolete files Brian Gix
2018-12-24 20:57 ` Marcel Holtmann
2018-12-19 4:19 ` [PATCH BlueZ v5 03/30] mesh: Utilities for DBus support Brian Gix
2018-12-24 21:01 ` Marcel Holtmann
2018-12-19 4:19 ` [PATCH BlueZ v5 04/30] mesh: Internal errors Brian Gix
2018-12-24 21:03 ` Marcel Holtmann
2018-12-19 4:19 ` [PATCH BlueZ v5 05/30] mesh: Rewrite storage for Multiple Nodes Brian Gix
2018-12-24 21:05 ` Marcel Holtmann
2018-12-19 4:19 ` [PATCH BlueZ v5 06/30] mesh: Rewrite Node handling for multiple nodes Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 07/30] mesh: Rewrite Network layer " Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 08/30] mesh: Direction agnostic PB-Adv implementation Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 09/30] mesh: Acceptor side provisioning implementation Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 10/30] mesh: Initiator " Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 11/30] mesh: Rewrite Controler interface for full init Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 12/30] mesh: Unchanged variables set to const Brian Gix
2018-12-19 4:19 ` [PATCH BlueZ v5 13/30] mesh: centralize generic utilities Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 14/30] mesh: re-arrange provisioning for DBus API Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 15/30] mesh: Re-architect " Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 16/30] mesh: Make config model handle multiple nodes Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 18/30] mesh: restructure I/O for " Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 19/30] mesh: Restructure DB to support " Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 20/30] mesh: restructure model services for " Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 21/30] mesh: DBUS interface for Provisioning Agent Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 22/30] mesh: restructure App Key storage Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 23/30] mesh: Clean-up Comment style Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 24/30] mesh: Update for DBus API and multi-node support Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 25/30] mesh: Add default location for Mesh Node storage Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 26/30] mesh: Add structural changes for mesh Brian Gix
2018-12-19 4:20 ` [PATCH BlueZ v5 27/30] mesh: Sample Provisioning Agent Brian Gix
2018-12-24 21:09 ` Marcel Holtmann
2018-12-27 19:22 ` Gix, Brian
2018-12-19 4:20 ` [PATCH BlueZ v5 28/30] mesh: Sample On/Off Client and Server Brian Gix
2018-12-24 21:10 ` Marcel Holtmann
2018-12-19 4:20 ` [PATCH BlueZ v5 30/30] mesh: Enable building Mesh Daemon Brian Gix
2018-12-24 21:12 ` Marcel Holtmann
2018-12-23 17:54 ` [PATCH BlueZ v5 00/30] Major rewrite for Multi-Node and DBus Gix, Brian
[not found] ` <20181219042016.25538-30-brian.gix@intel.com>
2018-12-24 21:10 ` [PATCH BlueZ v5 29/30] mesh: Sample Mesh Joiner (provision acceptor) 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=20181219042016.25538-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=johan.hedberg@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;
as well as URLs for NNTP newsgroup(s).