All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Gix <bgix@codeaurora.org>
To: claudio.takahasi@openbossa.org
Cc: linux-bluetooth@vger.kernel.org
Subject: Attribute Server and Client TODOs
Date: Fri, 21 Jan 2011 16:07:56 -0800	[thread overview]
Message-ID: <1295654876.1774.24.camel@ubuntuLab1> (raw)

Hi Claudio, etc,

Sorry for the repeat --> I sent it to the incorrect list the first time.

We are starting to look at the adopted LE profiles, and it is becoming
clear that Higher layer (Applications etc) server support will be needed
for some of the significant use cases such as Proximity.  Is anybody
currently working on a D-Bus interface to the Attribute Server?  I know
there is nothing in code that has been up-streamed yet, but I was
wondering if anyone has put some thought into what a D-Bus interface for
the Attribute Server might look like?

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.


Thanks for your time.


-- 
Brian Gix
bgix@codeaurora.org
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum


             reply	other threads:[~2011-01-22  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-22  0:07 Brian Gix [this message]
2011-01-22  7:21 ` Attribute Server and Client TODOs Erin Yueh
2011-01-27 19:30   ` Inga Stotland
2011-01-28  6:03     ` Erin Yueh
  -- 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=1295654876.1774.24.camel@ubuntuLab1 \
    --to=bgix@codeaurora.org \
    --cc=claudio.takahasi@openbossa.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.