anchao commented on code in PR #20686:
URL: https://github.com/apache/nuttx/pull/20686#discussion_r4285330343
##########
net/Kconfig:
##########
@@ -438,6 +390,7 @@ source "net/netlink/Kconfig"
source "net/tcp/Kconfig"
source "net/udp/Kconfig"
source "net/bluetooth/Kconfig"
+source "net/bt/Kconfig"
Review Comment:
This doesn't conflict with the existing Bluetooth subsystem at all — the new
stack lives under net/bt/ and is guarded by its own CONFIG_BT Kconfig option,
completely independent from the legacy stack. The two can coexist and be
developed in parallel.
Submitting to the community early has several benefits:
1. Parallel development: The community can start testing, reviewing, and
contributing fixes while we continue working on phase 2 (userspace/kernel space
split). There's no need to block the initial framework on downstream work.
2. Earlier feedback: The Bluetooth stack is a large piece of work — 600+
files. Getting it into the tree sooner means more eyes on the code, earlier bug
discovery, and broader testing across different hardware platforms.
3. Lower upstream maintenance burden: Keeping a large patch set in an
internal fork and rebasing against master is painful and error-prone. Every day
it stays out of tree, the merge conflict surface grows.
Asking us to fully finish phase 2 and 3 in isolation before submitting phase
1 would actually slow down the overall effort and delay the community from
benefiting from a working Bluetooth stack. This is a baseline submission that
gives everyone a foundation to build on — not the final product.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
