Linux-Bluetooth Archive on lore.kernel.org
 help / Atom feed
* [PATCH BlueZ] mesh: Add README file
@ 2019-02-01  0:22 Inga Stotland
  2019-02-04 20:10 ` Gix, Brian
  0 siblings, 1 reply; 2+ messages in thread
From: Inga Stotland @ 2019-02-01  0:22 UTC (permalink / raw)
  To: linux-bluetooth; +Cc: luiz.von.dentz, brian.gix, Inga Stotland

    This file contains instructions for Bluetooth mesh daemon
    configuration and description of the persistent storage.
---
 mesh/README | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 50 insertions(+)
 create mode 100644 mesh/README

diff --git a/mesh/README b/mesh/README
new file mode 100644
index 000000000..151a1e6a1
--- /dev/null
+++ b/mesh/README
@@ -0,0 +1,50 @@
+Bluetooth Mesh Daemon
+*********************
+
+Copyright (C) 2019  Intel Corporation. All rights reserved.
+
+Compilation and installation
+============================
+
+In addition to main BlueZ requirements, MeshCtl needs the following:
+	- json-c library
+
+Configuration and options
+=========================
+
+	--enable-mesh
+
+		Build mesh daemon and other Bluetooth Mesh based tools
+
+Current implementation of the mesh daemon requires exclusive access to
+a Bluetooth controller.
+The AutoEnable option in the installed main.conf should be set to "false".
+
+Storage
+=======
+
+Default storage directory is /var/lib/bluetooth/mesh.
+
+The directory contains the provisioned nodes configurations.
+Each node has its own subdirectory, named with a 4-digit (hexadecimal)
+identificator that is internally generated by the mesh daemon at the time
+of the node provisioning.
+
+Each subdirectory contains the following files:
+	- node.json:
+		node configuration and is populated by the
+		daemon based on the configuration commands from a
+		provisioner/configuration client
+	- node.json.bak:
+		a backup that the last known good node configuration.
+
+The files are in JSON format.
+
+Information
+===========
+
+Mailing lists:
+	linux-bluetooth@vger.kernel.org
+
+For additional information about the project visit BlueZ web site:
+	http://www.bluez.org
\ No newline at end of file
-- 
2.17.2


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH BlueZ] mesh: Add README file
  2019-02-01  0:22 [PATCH BlueZ] mesh: Add README file Inga Stotland
@ 2019-02-04 20:10 ` Gix, Brian
  0 siblings, 0 replies; 2+ messages in thread
From: Gix, Brian @ 2019-02-04 20:10 UTC (permalink / raw)
  To: linux-bluetooth, Stotland, Inga; +Cc: Von Dentz, Luiz


Applied

On Thu, 2019-01-31 at 16:22 -0800, Inga Stotland wrote:
>     This file contains instructions for Bluetooth mesh daemon
>     configuration and description of the persistent storage.
> ---
>  mesh/README | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 50 insertions(+)
>  create mode 100644 mesh/README
> 
> diff --git a/mesh/README b/mesh/README
> new file mode 100644
> index 000000000..151a1e6a1
> --- /dev/null
> +++ b/mesh/README
> @@ -0,0 +1,50 @@
> +Bluetooth Mesh Daemon
> +*********************
> +
> +Copyright (C) 2019  Intel Corporation. All rights reserved.
> +
> +Compilation and installation
> +============================
> +
> +In addition to main BlueZ requirements, MeshCtl needs the following:
> +	- json-c library
> +
> +Configuration and options
> +=========================
> +
> +	--enable-mesh
> +
> +		Build mesh daemon and other Bluetooth Mesh based tools
> +
> +Current implementation of the mesh daemon requires exclusive access to
> +a Bluetooth controller.
> +The AutoEnable option in the installed main.conf should be set to "false".
> +
> +Storage
> +=======
> +
> +Default storage directory is /var/lib/bluetooth/mesh.
> +
> +The directory contains the provisioned nodes configurations.
> +Each node has its own subdirectory, named with a 4-digit (hexadecimal)
> +identificator that is internally generated by the mesh daemon at the time
> +of the node provisioning.
> +
> +Each subdirectory contains the following files:
> +	- node.json:
> +		node configuration and is populated by the
> +		daemon based on the configuration commands from a
> +		provisioner/configuration client
> +	- node.json.bak:
> +		a backup that the last known good node configuration.
> +
> +The files are in JSON format.
> +
> +Information
> +===========
> +
> +Mailing lists:
> +	linux-bluetooth@vger.kernel.org
> +
> +For additional information about the project visit BlueZ web site:
> +	http://www.bluez.org
> \ No newline at end of file
^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-01  0:22 [PATCH BlueZ] mesh: Add README file Inga Stotland
2019-02-04 20:10 ` Gix, Brian

Linux-Bluetooth Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-bluetooth/0 linux-bluetooth/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-bluetooth linux-bluetooth/ https://lore.kernel.org/linux-bluetooth \
		linux-bluetooth@vger.kernel.org linux-bluetooth@archiver.kernel.org
	public-inbox-index linux-bluetooth


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-bluetooth


AGPL code for this site: git clone https://public-inbox.org/ public-inbox