As mentioned in the title, this is just an experimental project that needs to
discuss further the implementation of the bluetooth stack.
The implementation of bt stack in userspace does not conflict with the current
architecture, this is just a choice.
On the contrary, the complete BLE+MESH solution will help for some developers
to announce their products more quickly,
which is very helpful for NuttX promotion.
Certainly is a choice for you and your products, but it must never come
into the NuttX repositories. I really wish you good luck, but NuttX is
going a different way and this will not be accepted upstream.
However, from 2018 to 2020, after Greg completed the stack initial version,
until now, the NuttX stack does not have any enhancements, In userspace, btsak
lacks a lot of important functions and features, such as MESH, A2DP have not
yet been implemented.
There have been a few updates but no major enhancements. I was hoping
that there would be but you chose to go a incompatiable and unacceptable
direction. That is too bad. Such a waste of an opportunity to
collborate. But you design prohibits that.
We discovered during the evaluation at the beginning of the project that if we
have an urgent product launch cycle,
then we will invest a lot of HC and resources to maintain this stack, the
investment here is uncertain, seriously, this is not a sane approach.
So now there is a practical problem in front of us，If we have a large number of
product lines that need to use MESH and A2DP on nuttx, what should we do?
how about SIG certification? I think it's a problem that many developers will
faced, and it's also an important metrics to choose OS.
The values and decisions of commercial product development is different
from the values of a good open source project. What you are suggesting
is not a sane approach for an open source project.
What you should do is to coordinate and and cooperate with the NuttX
team to get help from the community. If you chose to go your own way
and not discussion or cooperation with the team, then you are on your
own. That code will not come into the repository.
If you want to do things correctly and get the benefit of community
support then you need to communicate, conform, and cooperate. You help
would be appreciated. The current direction you are taking is NOT
appreciated and is a waste of your time in the long run. It will not be
adopted. I will never come into the repositories. It will never be
supported or used by anyone other than Xiaomi.
If you want the benefit of working in an open source project, be part of
the team and follow the project architecture and roadmap. Taking you own
rogue direction isolates you. You will fail in the direction you are
taking.
What can NuttX bring to us? In addition to a stable OS, I think a complete and
highly integrated net stack will be a great place.
Zephyr ble+mesh stack will only be one of the BLE solutions. In the future,
Xiaomi will complete the bluedroid porting of NuttX to bring support for the
A2DP part.
NEVER in user space. NEVER via character drivers. NEVER!
