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.
I fully agree with @btashton @v01d, According to the current implementation of nuttx, the socket model will be a perfect solution to solve the compatibility issue between userspace and kernelspace. I am not exclusive, and hope that PMC can enhance further the current bt stack implementation. 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. 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. 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. As I said at the beginning, this is just a solution to let NuttX developers know that the current OS has a reliable stack support. Of course, Roadmap of NuttX has not changed, and the socket model is still under development. BRs, ________________________________________ 发件人: Gregory Nutt <spudan...@gmail.com> 发送时间: 2020年8月26日 21:47 收件人: dev@nuttx.apache.org 主题: [External Mail]Re: defining a BLE GATT server On 8/24/2020 8:51 AM, Matias N. wrote: > Thanks for the heads up. Would be good to get Xiao Xiang's input on this > then. Maybe he already encountered this issue. > > For now I'm working on the Link Layer, looking at 4.0 spec as a start. > If the host layer is reimplemented for 5.0 I understand it shouldn't > invalidate > the LL in principle. But for any change on the host layer I would like to > know if there are plans or work in progress. > > On Mon, Aug 24, 2020, at 11:47, Gregory Nutt wrote: >> Also, I understand that Xiaomi intends to replace the entire Bluetooth >> stack with a newer BT 5.0 stack. I don't know if that is still a plan >> of record or not, but you probably should coordinate Bluetooth >> architectural changes with Xiao Xiang in any event. >> Based on the discussions, I don't think you need to be concerned with the directions Xiaomi is taking. They have gone rogue and are ignoring the roadmap. Their code will never come into NuttX. #/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ This e-mail and its attachments contain confidential information from XIAOMI, which is intended only for the person or entity whose address is listed above. Any use of the information contained herein in any way (including, but not limited to, total or partial disclosure, reproduction, or dissemination) by persons other than the intended recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender by phone or email immediately and delete it!******/#
