Hi Greg, Brennan Okay, it is enough, I think we have all spent enough time discussing this issue!
I agree that this change will not be upstream, Xiaomi will not give up NuttX's Roadmap, which is also Xiang's long-cherished wish. I will abandon later, Thanks for your precious time. BRs, ________________________________________ 发件人: Brennan Ashton <bash...@brennanashton.com> 发送时间: 2020年8月27日 1:01 收件人: dev@nuttx.apache.org 主题: Re: 答复: [External Mail]Re: defining a BLE GATT server On Wed, Aug 26, 2020 at 9:56 AM Gregory Nutt <spudan...@gmail.com> wrote: > > 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. > > I still would not accept any such change in the OS. And, if merged, I > would feel compelled to revert the commits. I'm agreeing with you Greg, anything that comes into Apps or the OS must use the socket API. All I am saying is there are applications like dumping the HCI log that really just pretty print the packets. It does not care if it came via a socket or something else. As long as it uses the NuttX API there is no reason to build it twice. --Brennan #/******本邮件及其附件含有小米公司的保密信息，仅限于发送给上面地址中列出的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本邮件！ 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!******/#
