All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Urbani, Edmund" <edmund.urbani@lilandit.com>
To: unlisted-recipients:; (no To-header on input)
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: How to get started on a GATT Server ?
Date: Tue, 04 Nov 2014 13:04:29 +0100	[thread overview]
Message-ID: <5458C0CD.9010907@LilandIT.com> (raw)
In-Reply-To: <CAHrH25RfMAiNTHYBR=vT+KuBtVwEKPuLRFfEiMGF9Ya__9Y5nA@mail.gmail.com>


On 11/03/2014 08:32 PM, Arman Uguray wrote:
> Hi Edmund,
>
>> On Mon, Nov 3, 2014 at 7:38 AM, Urbani, Edmund <edmund.urbani@lilandit.com> wrote:
>> Hello all,
>>
>> I am trying to write a simple GATT-based service of my own. Right now I
>> don't really know which docs I should be looking at. I have skimmed through
>> bluez sources (5.23) and found gatt-service.h and gatt.h, as well as the
>> gatt-example plugin.
>>
>> So far I am still trying to figure out whether I should be going the C API
>> route or maybe use the D-Bus interface. Also gatt-service.c seems to suggest
>> that there is a way to register a GATT service over D-Bus but running it
>> gives me this:
>> RegisterService: Method "RegisterService" with signature "oa{sv}" on
>> interface "org.bluez.GattManager1" doesn't exist"
> The reason you're not seeing GattManager1 is because it's hidden
> behind the "experimental" flag. So you need to configure and run bluez
> with the --enable-experimental and the --experimental flags
> respectively.
>
> That said, that API implementation isn't complete and isn't in fact
> even wired up with the internal attrib-server. We're working towards
> rewriting all of the C API and finally implementing the proposed D-Bus
> API but until then, I would ignore doc/gatt-api.txt (it's only a
> proposal at the moment and isn't even included in release tarballs).
> So for now you have to use the C API route. There will probably be an
> announcement once that D-Bus API is finally supported.

>> Any pointers to help me get started would be appreciated. Thanks!
>>
>> Kind regards,
>>    Edmund
> Cheers,
> Arman

Thanks, I won't bother with the D-Bus interface then. But if the C API is being 
rewritten now, that sounds like there is currently no stable API available at 
all. :/ Or is it just the internals being rewritten?

So I assume, the fastest route the get a prototype that does something, would be 
to get gatt-example.c to run and then modify that, right?

Kind regards,
  Edmund


  reply	other threads:[~2014-11-04 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 15:38 How to get started on a GATT Server ? Urbani, Edmund
2014-11-03 19:32 ` Arman Uguray
2014-11-04 12:04   ` Urbani, Edmund [this message]
2014-11-04 19:11     ` Arman Uguray
2014-11-05 17:21       ` Urbani, Edmund
2014-11-05 17:47         ` Arman Uguray
2014-11-07 14:10           ` Urbani, Edmund
2014-11-07 20:32             ` Arman Uguray

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5458C0CD.9010907@LilandIT.com \
    --to=edmund.urbani@lilandit.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.