From: Junho Lee <tot0roprog@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Applying Mesh Protocol 1.1 specification
Date: Thu, 22 Aug 2024 18:13:55 +0900 [thread overview]
Message-ID: <66c70155.170a0220.2e0a01.d9c0@mx.google.com> (raw)
Hi,
I found that the bluetooth-mesh part has not applied SIG Mesh Protocol
1.1 specification yet. I would like to update various changes to the
specification, such as SAR transmitter/receiver state.
For example, in the line corresponding to the link below, I don't
understand why it sends a segmented message for a multicast address a
fixed number of times, 4 times. This is causing performance issues with
my product.
https://github.com/bluez/bluez/blob/master/mesh/net.c#L3335
Most of the mesh/net.c code was last written 4 or 6 years ago and is out
of date with Mesh Protocol 1.1. Is there a reason for not applying Mesh
Protocol 1.1 or is anyone working on?
Regards,
Junho Lee
next reply other threads:[~2024-08-22 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 9:13 Junho Lee [this message]
2024-08-25 22:48 ` Applying Mesh Protocol 1.1 specification 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=66c70155.170a0220.2e0a01.d9c0@mx.google.com \
--to=tot0roprog@gmail.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