You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2018/05/02 13:50:41 UTC

[GitHub] andrzej-kaczmarek commented on issue #72: [RFC] Porting NimBLE

andrzej-kaczmarek commented on issue #72: [RFC] Porting NimBLE
URL: https://github.com/apache/mynewt-nimble/pull/72#issuecomment-385984360
 
 
   Last two commits update NPL to include "native" API, i.e. functions and structs are not the same as Mynewt but are specific to NimBLE. This means we do not explicitly depend on Mynewt API and also Mynewt will need its porting layer (although new function APIs are pretty similar to Mynewt's so it should not be a big problem here).
   
   This means we have single `porting/nimble/include/nimble/nimble_npl.h` file which is a common definition for all APIs and structures are defined in `nimble/nimble_npl_os.h` for each NPL in OS-specific manner. I guess this is what is expected here.
   
   However, some changes are still required to NimBLE code to fully utilize these APIs since some of them do not exist in Mynewt and basically wrap operations that are now done by accessing various structures directly.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services