Hi Yon,
On 24/01/17 15:53, yon ar c'hall wrote:
> Hi Felipe,
>
> On Tue, Jan 24, 2017 at 3:45 PM, Felipe Ferreri Tonello
> <eu@xxxxxxxxxxxxxxxxx> wrote:
>
>> plugin/gatt-example.c is not in the repository, as it is relevant
>> anymore. gatt-example implemented a gatt-server using older deprecated API.
>
> Oops, I made a typo : the sub-folder is "plugins" (with "s"), not
> "plugin", and it's still in the bluez archive (5.43).
That is true, but it is still not usable anymore. From git log:
commit cc80afff47938a2c93aff0f7904fd937e6333908
Author: Luiz Augusto von Dentz <luiz.von.dentz@xxxxxxxxx>
Date: Tue Nov 8 11:00:28 2016 +0200
build: Remove gatt-example plugin
This examples can be done over D-Bus already so it makes no sense to
have
it as a plugin and in fact it currently it doesn't even work since
it was
never ported to the new code under src/shared.
>
>> Anyway, there are two ways to implement a GATT client profile (Central
>> role). As a generic bluetoothd plugin that will export an API to
>> applications via D-Bus, more likely.
>
> We didn't find any source of a bluetoothd plugin implementing a GATT
> LE profile (such as those listed on http://www.bluez.org/profiles/ :
> HTP, HoG,...). Sorry, we're still missing something... Would there be
> any piece of doc that could help for creating a bluetoothd plugin, as
> it looks to be the correct way to proceed ?
Not really. Just source code.
You can check profile implementations under profiles/ and then just
check the code there.
>
>> Or in your own application using the GATT D-Bus API that bluetoothd exports.
>> test/example-gatt-client implements the Heart Rate profile quite simply
>> using the D-Bus API.
>
> We do understand the Python code of test/example-gatt-client :-) It
> clearly helps to get the whole picture.
> Thanks for the pointer.
>
--
Felipe
Attachment:
0x92698E6A.asc
Description: application/pgp-keys
