All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gix, Brian" <brian.gix@intel.com>
To: "linux-bluetooth@vger.kernel.org"
	<linux-bluetooth@vger.kernel.org>,
	"Stotland, Inga" <inga.stotland@intel.com>
Cc: "Von Dentz, Luiz" <luiz.von.dentz@intel.com>
Subject: Re: [PATCH BlueZ] TODO: Add Bluetooth mesh items
Date: Mon, 4 Feb 2019 20:10:16 +0000	[thread overview]
Message-ID: <1549311015.22761.0.camel@intel.com> (raw)
In-Reply-To: <20190204191534.5221-1-inga.stotland@intel.com>



Applied



On Mon, 2019-02-04 at 11:15 -0800, Inga Stotland wrote:
> ---
>  TODO | 51 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 51 insertions(+)
> 
> diff --git a/TODO b/TODO
> index d88349e06..37462d6e8 100644
> --- a/TODO
> +++ b/TODO
> @@ -186,3 +186,54 @@ ATT/GATT (new shared stack)
>  
>  Management Interface
>  ====================
> +
> +Mesh
> +====
> +- Read default configuration settings (e.g., provisioning timeout, supported
> +  features, etc.)from  mesh.conf file.
> +
> +  Priority: Medium
> +  Complexity: C1
> +
> +- Add examples and unit tests
> +
> +  Priority: High
> +  Complexity: C1
> +
> +- Implement unified feature management mechanism for mesh nodes that are hosted
> +  on the same device
> +
> +  Priority: Medium
> +  Complexity: C2
> +
> +- Implement mandatory Health Server model. Most likely, this will involve
> +  additions to mesh D-Bus API
> +
> +  Priority: Medium
> +  Complexity: C2
> +
> +- Design and implement Mesh Provisioner/ Configuration Client Model.
> +
> +  Priority: Medium
> +  Complexity: C3
> +
> +- Add support for GATT proxy server
> +
> +  Priority: Low
> +  Complexity: C3
> +
> +- Merge common functionality from tools/mesh. Ideally, source code from the
> +  tools/mesh directory should completely dissapear.
> +
> +  Priority: Low
> +  Complexity: C2
> +
> +- Support for Low Power Node (LPN)
> +
> +  Priority: Low
> +  Complexity: C4
> +
> +- Support for all the Provisionings OOB styles
> +
> +  Priority: Medium
> +  Complexity: C2

      reply	other threads:[~2019-02-04 20:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 19:15 [PATCH BlueZ] TODO: Add Bluetooth mesh items Inga Stotland
2019-02-04 20:10 ` Gix, Brian [this message]

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=1549311015.22761.0.camel@intel.com \
    --to=brian.gix@intel.com \
    --cc=inga.stotland@intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.von.dentz@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.