Let me clarify one thing: The approach we take is a pure userspace solution, it isn't related to NuttX kernel and no plan to upstream it. The major difference is where to put L2CAP/HCI code(userspace v.s. kernelspace) and it isn't too hard to migrate to socket interface once the NuttX kernel has the full and stable L2CAP/HCI support. My question is how to finish the Bluetooth stack on the userspace? It will be a huge work to write from scratch(BT, BLE, BLE mesh and BLE Audio).
> -----Original Message----- > From: Gregory Nutt <spudan...@gmail.com> > Sent: Thursday, August 27, 2020 12:46 AM > To: dev@nuttx.apache.org > Subject: Re: 答复: 答复: [External Mail]Re: defining a BLE GATT server > > > > Mr.Greg, I really don't understand why you are so angry, and there are so > > many verbal attacks. > > I just share a feasibility. What I expect is discussion and respect, not > > devaluation. If you don't like it, just say it like others. > > Yes, I am angry. I am very pissed off that you completely ignored the NuttX > architectural roadmap and chose to go your own > direction. That is offensive (as well as stupid). And I do not want to work > with people who cannot work together for common > architectural goals. The direction you are taking is not going to lead to > friendship or cooperation. > > Attempts like these to destroy the NuttX architecture will always piss me > off. I have a lot invested in this OS and some ignorant > engineer who ignores that legacy is going make me angry. You would ruin this > OS! > > You must keep these changes within Xaiomi because they will not be permitted > upstream. >
