Lets bring this back to a constructive place. An Chao I really appreciate the detailed information that you wrote, while I don't think it will be appropriate to include directly upstream it is still valuable to know how you are trying to use this and it helps us make an informed decision moving forward. I think we are going to take more of the BlueZ path forward but I suspect there are ways to allow your internal works to sit nicely on top of that without compromising what we are building here. You see this even in the Linux Kernel where for very specific use cases companies will implement parts of a network stack in user space.
Greg I fully understand where you stand and your frustration, you have put a significant part of your life into this project and want to see it grow and not erode. In this case I think you have multiple people on the team who are also saying thanks, but lets make sure we are doing this correctly and not taking shortcuts. Lets try to see how we can move this forward, I'm not fully sure I fully understand the implications of what you were saying about the packet protocol, but I think it is best that we focus the discussion on that in the GitHub issue that I opened about the HCI socket. I can share what I know about the BlueZ interface there with some client examples as appropriate. I'm sure we can find ways to bridge the gap here especially on the application side. --Brenna On Wed, Aug 26, 2020 at 9:41 AM 安超 <anc...@xiaomi.com.invalid> wrote: > > 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. > > BRs, > > ________________________________________ > 发件人: Gregory Nutt <spudan...@gmail.com> > 发送时间: 2020年8月27日 0:30 > 收件人: dev@nuttx.apache.org > 主题: Re: 答复: [External Mail]Re: defining a BLE GATT server > > > 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. > > Imagine what we could accomplish if we worked together instead you > taking off unilaterally on your own unacceptable, bullshit direction! > We could do a lot which such a terrible solution. We could implement > the roadmap. We could maintain Linux compatible. We could be the world > class implementation, not some sleazy little sneaks illicit Zephyr code > into the code base and then uses it is a moronic, incompatible way. > > What you are doing is very bad and would be a disaster for the OS. We > have to resist this in all ways that we are able to. > > Of course, if Xiaomi likes this shitty architecture and back-door access > to Zephyr code, go ahead. Just don't degrade the NuttX project with > this garbage. We won't permit that. > > #/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ > 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!******/#
