From c2053ffc231d7b9237fe987f96a222f764f4ca56 Mon Sep 17 00:00:00 2001 From: Andrzej Kaczmarek Date: Tue, 2 Jul 2019 14:12:53 +0200 Subject: [PATCH] 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 f80ec9771..137d6e94f 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)