Hello Anderson, >>> Covers the Proximity Reporter for Link Loss, Tx Power and Immediate [clip ...] >> Is this >> good enough to implement both sides of the profile, or just one side of >> it? > >The API is for the Proximity Monitor role. Sounds bit confusing.. Ain't these API's being proposed for Proximity Reporter Role which is what Claudio mentioned in the original RFC? Which bring me to the next question- since a GATT client makes more sense for a dual mode stack such as Bluez, shouldn't we focus first on Monitor kind of roles for LE profiles and later consider Reporter type roles for testing only? >The Proximity Reporter role >will usually run on LE single mode (very low power, coin cell battery) >devices, but we will have a basic Proximity Reporter for testing >purposes as well, which could be later expanded to a full featured >Reporter. > >> Is this something that could require UI being written? > >For sure. This is just the D-Bus API, some graphical/console >application must be written to use it. We will provide test scripts >under the test/ directory. Thanks, Arun -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
