From: Christian Eggers <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5810cb: mesh: acceptor: increase interval for unprovisione...
Date: Tue, 01 Jul 2025 07:55:46 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/977765/000000-189ecb@github.com> (raw)
Branch: refs/heads/977765
Home: https://github.com/bluez/bluez
Commit: 5810cb647382acdd368fe31e568ad36b4318c185
https://github.com/bluez/bluez/commit/5810cb647382acdd368fe31e568ad36b4318c185
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M mesh/prov-acceptor.c
Log Message:
-----------
mesh: acceptor: increase interval for unprovisioned device beacon
I cannot find a specific interval for sending unprovisioned device
beacons in MshPRT_v1.1, section 3.10.2/5.2.1. The current interval of
500 ms seems to cause interferience with normal advertising messages,
maybe this is controller dependent (seen on RTL8761BU).
A beacon interval of 1000 ms should be sufficient for scanning (e.g. by
a provisioner) while allowing normal advertising messages to be
transmitted.
Commit: 796b0e6a6588b63354ee3733ffc589982ecfa62a
https://github.com/bluez/bluez/commit/796b0e6a6588b63354ee3733ffc589982ecfa62a
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M Makefile.mesh
A mesh/gatt-service.c
A mesh/gatt-service.h
A mesh/pb-gatt.c
A mesh/pb-gatt.h
M mesh/prov-acceptor.c
Log Message:
-----------
mesh: add support for provisioning via GATT
ToDo: Consider moving dbus_client instance into separate singleton, so
that no destruction/construction is necessary when switching from GATT
provisioning service to GATT proxy service (see next commit).
Commit: fb20d62fda1d971e0e0679866f109c353ab1de93
https://github.com/bluez/bluez/commit/fb20d62fda1d971e0e0679866f109c353ab1de93
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M Makefile.mesh
A mesh/gatt-proxy-svc.c
A mesh/gatt-proxy-svc.h
M mesh/main.c
M mesh/net-keys.c
M mesh/net-keys.h
M mesh/net.c
M mesh/net.h
M mesh/prov-acceptor.c
Log Message:
-----------
mesh: add GATT proxy service
FIXME: net.c: determine whether data shall be sent via mesh_io or
gatt_proxy
Commit: 189ecb870d7baecc6b5aa96df9d39948117198e5
https://github.com/bluez/bluez/commit/189ecb870d7baecc6b5aa96df9d39948117198e5
Author: Christian Eggers <ceggers@arri.de>
Date: 2025-07-01 (Tue, 01 Jul 2025)
Changed paths:
M Makefile.mesh
M mesh/crypto.c
M mesh/crypto.h
M mesh/net-keys.c
M mesh/net-keys.h
M mesh/net.c
A mesh/proxy-cfg.c
A mesh/proxy-cfg.h
Log Message:
-----------
mesh: initial support for proxy configuration messages via GATT
Implement reception and response for Proxy Configuration Messages
(MshPRT_v1.1, section 6.6).
ToDo: Apply configured filters.
Compare: https://github.com/bluez/bluez/compare/5810cb647382%5E...189ecb870d7b
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2025-07-01 14:55 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=bluez/bluez/push/refs/heads/977765/000000-189ecb@github.com \
--to=noreply@github.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox