From: Jeremy Hiatt <jeremy@brilliant.tech>
To: linux-bluetooth@vger.kernel.org
Subject: Mesh support roadmap
Date: Mon, 18 Sep 2017 19:54:12 -0700 [thread overview]
Message-ID: <CAEa75K0F-8O7AmH_qu4s6GLaMVdxdNLSdnTyeQi5uUyaQM5eKw@mail.gmail.com> (raw)
I'm very excited to see that initial mesh support has made it into the
latest BlueZ release. My understanding is that so far there's no
support for participating in the mesh network, i.e. acting to
relay/re-broadcast messages. Is there any active work in this area, or
future plans to incorporate this into BlueZ?
reply other threads:[~2017-09-19 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAEa75K0F-8O7AmH_qu4s6GLaMVdxdNLSdnTyeQi5uUyaQM5eKw@mail.gmail.com \
--to=jeremy@brilliant.tech \
--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 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.