From: "Inga Stotland" <ingas@codeaurora.org>
To: "'Erin Yueh'" <erinyueh@gmail.com>
Cc: "'Brian Gix'" <bgix@codeaurora.org>, <linux-bluetooth@vger.kernel.org>
Subject: RE: Attribute Server and Client TODOs
Date: Thu, 27 Jan 2011 11:30:02 -0800 [thread overview]
Message-ID: <000001cbbe58$982b5fd0$c8821f70$@org> (raw)
In-Reply-To: <AANLkTi=gLKMvWuUeyjqGBQuWd5ztjjr10d44H4A1fFfZ@mail.gmail.com>
Hi Erin,
> Also, one of my compatriots is telling me that she cannot get the GATT
> Client D-Bus interface to work. I don't know if this is a simple lack
> of Introspection Data (required by d-feet), or if there is a build or
> configuration parameter that needs to be setup. I have just been using
> the gatttool to run my tests, and not going through D-Bus. If anybody
> has been using D-Bus for GATT Client testing, I would be interested in
> finding out if there is some setup requirements that I am missing.
>
I only modified EnableLE and AttributeServer two values in main.conf and
add --enable-attribute on building bluez. Then, it can work. I can use dbus-send
to query data. I also wrote the notes about setting up gatttool in bluez over
BR/EDR.
http://i-miss-erin.blogspot.com/2010/12/gatttool-in-bluez-over-bredr.html
> Thanks for your time.
>
>
> --
> Brian Gix
Thanks,
Erin Yueh
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)?
Thanks,
Inga Stotland
ingas@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next prev parent reply other threads:[~2011-01-27 19:30 UTC|newest]
Thread overview: 4+ 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 [this message]
2011-01-28 6:03 ` Erin Yueh
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='000001cbbe58$982b5fd0$c8821f70$@org' \
--to=ingas@codeaurora.org \
--cc=bgix@codeaurora.org \
--cc=erinyueh@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox