From: Junho Lee <tot0roprog@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: bggixx@gmail.com
Subject: [PATCH BlueZ 0/4] mesh: Fix segmentation behavior of Lower transport layer
Date: Fri, 4 Oct 2024 16:30:39 +0900 [thread overview]
Message-ID: <66ff99a1.a70a0220.1fac1d.b37c@mx.google.com> (raw)
These is implementations of segmentation and reassembly, except for the
friend feature for LPN nodes, implemented according to Mesh Protocol 1.1
section 3.5.
Junho Lee (4):
mesh: Implement lower transport layer for segmentation and reassembly
mesh: Add mesh conf for SAR Transmitter and Receiver
mesh: Fix inserting NULL into bool type arguments to false
mesh: Add features of Segmented Control message
mesh/crypto.c | 69 ++--
mesh/mesh-main.conf | 107 ++++++
mesh/mesh.c | 125 ++++++-
mesh/mesh.h | 2 +
mesh/net.c | 868 ++++++++++++++++++++++++++++++--------------
mesh/net.h | 33 +-
6 files changed, 881 insertions(+), 323 deletions(-)
--
2.34.1
next reply other threads:[~2024-10-04 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 7:30 Junho Lee [this message]
2024-10-04 15:16 ` [PATCH BlueZ 0/4] mesh: Fix segmentation behavior of Lower transport layer Luiz Augusto von Dentz
2024-10-07 0:17 ` Junho Lee
2024-10-11 15:01 ` 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=66ff99a1.a70a0220.1fac1d.b37c@mx.google.com \
--to=tot0roprog@gmail.com \
--cc=bggixx@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