You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by an...@apache.org on 2019/07/12 15:51:31 UTC
[mynewt-nimble] branch master updated: nimble/transport: Add option
to use custom HCI transport
This is an automated email from the ASF dual-hosted git repository.
andk pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/mynewt-nimble.git
The following commit(s) were added to refs/heads/master by this push:
new c2053ff nimble/transport: Add option to use custom HCI transport
c2053ff is described below
commit c2053ffc231d7b9237fe987f96a222f764f4ca56
Author: Andrzej Kaczmarek <an...@codecoup.pl>
AuthorDate: Tue Jul 2 14:12:53 2019 +0200
nimble/transport: Add option to use custom HCI transport
Since it's recommended for apps to explicitly include only meta-package
for HCI transport (so it can be easily changed in target for any BSP),
we should also have an option to allow HCI transport other than one of
those we have in tree. This is useful for development and 3rd party
solutions which may have own HCI transport.
---
nimble/transport/syscfg.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/nimble/transport/syscfg.yml b/nimble/transport/syscfg.yml
index f80ec97..137d6e9 100644
--- a/nimble/transport/syscfg.yml
+++ b/nimble/transport/syscfg.yml
@@ -27,6 +27,7 @@ syscfg.defs:
restrictions: $notnull
choices:
- builtin # Built-in NimBLE controller and RAM transport
+ - custom # Custom transport, has to be included manually by user
- ram # RAM transport
- uart # UART HCI H4 transport
- socket # Socket transport (for native builds)