From: Erin Yueh <erinyueh@gmail.com>
To: Inga Stotland <ingas@codeaurora.org>
Cc: Brian Gix <bgix@codeaurora.org>, linux-bluetooth@vger.kernel.org
Subject: Re: Attribute Server and Client TODOs
Date: Fri, 28 Jan 2011 14:03:06 +0800 [thread overview]
Message-ID: <AANLkTinm=56sTExsyMgQSFkKCe5Ere8X4RY6aYxQugfS@mail.gmail.com> (raw)
In-Reply-To: <000001cbbe58$982b5fd0$c8821f70$@org>
Hi Inga,
On Fri, Jan 28, 2011 at 03:30, Inga Stotland <ingas@codeaurora.org> wrote:
[...]
> Thank you for your response about enabling GATT over D-Bus.
> I was following the instructions from your notes.
> However, when trying to test D-Bus operations for GATT, I cannot seem to get
> org.bluez.Characteristic interface to register...
> Have you been able to get GATT D-Bus interface to work just with BR/EDR (no LE)?
yup! I am able to use GATT related D-Bus interface to work with
BR/EDR. In the beginning, back to Bluez release 4.80, we can trigger
the discovering service when registering the client. Then it can store
few files in /var/lib/bluetooth/BT_ADDR. When we start bluetooth
daemon, it would register GATT D-Bus interface based on those files.
If you'd like to see those D-Bus interface, you could rollback to
release 4.80. You can use gatttoool to discover the primary service,
and copy 'primary', 'attributes' and 'characteristic' files. Then you
could use the latest Bluez, but move those files to the same folder.
You should be able to see the GATT D-Bus interface.
>
> Thanks,
>
> Inga Stotland
>
> ingas@codeaurora.org
> Employee of Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
>
Regards,
Erin Yueh
next prev parent reply other threads:[~2011-01-28 6:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 0:07 Attribute Server and Client TODOs Brian Gix
2011-01-22 7:21 ` Erin Yueh
2011-01-27 19:30 ` Inga Stotland
2011-01-28 6:03 ` Erin Yueh [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-21 19:39 Brian Gix
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='AANLkTinm=56sTExsyMgQSFkKCe5Ere8X4RY6aYxQugfS@mail.gmail.com' \
--to=erinyueh@gmail.com \
--cc=bgix@codeaurora.org \
--cc=ingas@codeaurora.org \
--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.