linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jose Antonio Santos Cadenas <santoscadenas@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Changes in HDP API
Date: Wed,  4 Aug 2010 09:49:11 +0200	[thread overview]
Message-ID: <1280908152-3743-1-git-send-email-santoscadenas@gmail.com> (raw)

This patch makes some changes in the HDP API based in the conversation that I
had yesterday with Luiz and Elvis.

I still have a doubt about the notification of devices in the agent. Luiz
commented that with this API the Agent and the Application could not be in
different processes, is this a problem?

An other open issue is: if we notify when a device is discovered and suitable
for connect with an application and when a devices is removed (or becomes not
suitable for connect). I think that we already need something like the patch
that we start discussing yesterday, something that can be called by the user
in order to force a new service discovery and notifies the driver that will
notify the agent. Of course we can avoid this not notifying the suitable
devices and just letting to try the connection against all the devices (if
there is no matching service it will fail). What do you think?

Regards.

Jose.


             reply	other threads:[~2010-08-04  7:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  7:49 Jose Antonio Santos Cadenas [this message]
2010-08-04  7:49 ` [PATCH] Changes in HDP API Jose Antonio Santos Cadenas
2010-08-04 13:09 ` Luiz Augusto von Dentz
2010-08-04 13:54   ` José Antonio Santos Cadenas
2010-08-04 16:45     ` Luiz Augusto von Dentz
2010-08-04 17:53       ` José Antonio Santos Cadenas
2010-08-04 18:22 ` Elvis Pfützenreuter
2010-08-05  9:29   ` José Antonio Santos Cadenas
2010-08-05 13:49     ` [PATCH] " Jose Antonio Santos Cadenas
2010-08-09 10:33       ` Santiago Carot-Nemesio
2010-08-10  8:01       ` José Antonio Santos Cadenas

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=1280908152-3743-1-git-send-email-santoscadenas@gmail.com \
    --to=santoscadenas@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;
as well as URLs for NNTP newsgroup(s).