Re: [BlueZ PATCH v2 1/3] doc: Introduce the Adv Monitor Device Lost event
From: Marcel Holtmann <marcel@holtmann.org>
Date: 2021-10-13 13:15:32
Hi Manish,
quoted hunk ↗ jump to hunk
Add a flag 'Device Tracked' to the existing 'Device Found' event to indicate that the controller has started tracking the device matching an Advertisement Monitor with handle 'Monitor_Handle'. Add a new event 'Adv Monitor Device Lost' to indicate that the controller has stopped tracking that particular device. --- Changes in v2: - Instead of creating a new 'Device Tracking' event, add a flag 'Device Tracked' in the existing 'Device Found' event and add a new 'Device Lost' event to indicate that the controller has stopped tracking that device. doc/mgmt-api.txt | 32 +++++++++++++++++++++++++++++++- 1 file changed, 31 insertions(+), 1 deletion(-)diff --git a/doc/mgmt-api.txt b/doc/mgmt-api.txt index 5355fedb0..0fd884ed0 100644 --- a/doc/mgmt-api.txt +++ b/doc/mgmt-api.txt@@ -107,7 +107,8 @@ Configuration command, Default Runtime Configuration Changed event, GetDevice Flags command, Set Device Flags command, Device Flags Changed event, Read Advertisement Monitor Features command, Add Advertisement Patterns Monitor command, Remove Advertisement Monitor command, Advertisement Monitor -Added event and Advertisement Monitor Removed event. +Added event, Advertisement Monitor Removed event, Updated Device Found event +and Added Advertisement Monitor Device Lost event. Example@@ -4247,6 +4248,7 @@ Device Found EventAddress_Type (1 Octet) RSSI (1 Octet) Flags (4 Octets) + Monitor_Handle (2 Octets) EIR_Data_Length (2 Octets) EIR_Data (0-65535 Octets)
you can not do this. This breaks ABI. Regards Marcel