From bce31c8da693275be6090acb66345988607edd2e Mon Sep 17 00:00:00 2001 From: Marcel Holtmann Date: Tue, 1 Jul 2014 12:58:08 +0200 Subject: [PATCH] doc: Introduce Non Connectable flag for Device Found event --- doc/mgmt-api.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt index 078435cd3..d51405c67 100644 --- a/doc/mgmt-api.txt +++ b/doc/mgmt-api.txt @@ -2162,6 +2162,7 @@ Device Connected Event The following bits are defined for the Flags parameter: 0 Reserved (not in use) 1 Legacy Pairing + 2 Reserved (not in use) Device Disconnected Event @@ -2332,6 +2333,7 @@ Device Found Event The following bits are defined for the Flags parameter: 0 Confirm name 1 Legacy Pairing + 2 Not Connectable The Confirm name flag indicates that the kernel wants to know whether user space knows the name for this device or not. If @@ -2346,6 +2348,10 @@ Device Found Event false-positives for this flag so user space should be able to handle getting something else as a PIN Request when pairing. + The Not Connectable flag indicates that the device will not + accept any connections. This can be indicated by Low Energy + devices that are in broadcaster role. + Discovering Event ================= -- 2.47.3