From: Brian Gix <brian.gix@intel.com>
To: linux-bluetooth@vger.kernel.org
Cc: luiz.dentz@gmail.com, brian.gix@intel.com, inga.stotland@intel.com
Subject: [PATCH BlueZ v4 0/2] Mesh demon switched to using kernel Mesh MGMT
Date: Thu, 22 Sep 2022 15:31:00 -0700 [thread overview]
Message-ID: <20220922223102.640173-1-brian.gix@intel.com> (raw)
This patchset enables the mesh daemon (bluetooth-meshd) to use the new
MGMT mesh opcodes and events to send and receive Mesh packets. By
default, the daemon attempts to enable the experimental mesh
functionality, and query the kernel for active mesh support before then
enumerating the available controllers and selecting ojne that works.
If no kernel support is found, it will continue to use a raw HCI socket
for mesh support.
v2-v3: Fix whitespace and spelling
v4: Rework missed 2 new files... readded.
Brian Gix (2):
mesh: Improve PB-ADV timing for reliability
mesh: Add new kernel MGMT based IO transport
Makefile.mesh | 9 +-
mesh/main.c | 39 +-
mesh/mesh-io-api.h | 11 +-
mesh/mesh-io-generic.c | 47 +--
mesh/mesh-io-mgmt.c | 788 +++++++++++++++++++++++++++++++++++++++++
mesh/mesh-io-mgmt.h | 11 +
mesh/mesh-io-unit.c | 13 +-
mesh/mesh-io.c | 188 +++++++---
mesh/mesh-io.h | 4 +-
mesh/mesh-mgmt.c | 164 +++++++--
mesh/mesh-mgmt.h | 12 +-
mesh/mesh.c | 6 +-
mesh/mesh.h | 2 +-
mesh/pb-adv.c | 9 +-
14 files changed, 1159 insertions(+), 144 deletions(-)
create mode 100644 mesh/mesh-io-mgmt.c
create mode 100644 mesh/mesh-io-mgmt.h
--
2.37.3
next reply other threads:[~2022-09-22 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 22:31 Brian Gix [this message]
2022-09-22 22:31 ` [PATCH BlueZ v4 1/2] mesh: Improve PB-ADV timing for reliability Brian Gix
2022-09-22 23:26 ` Mesh demon switched to using kernel Mesh MGMT bluez.test.bot
2022-09-22 22:31 ` [PATCH BlueZ v4 2/2] mesh: Add new kernel MGMT based IO transport 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=20220922223102.640173-1-brian.gix@intel.com \
--to=brian.gix@intel.com \
--cc=inga.stotland@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox