linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anderson Lizardo <anderson.lizardo@openbossa.org>
To: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>,
	linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ] device: Fix doing sdp discovery for LE devices
Date: Sat, 4 Feb 2012 08:14:05 -0400	[thread overview]
Message-ID: <CAJdJm_OFcUNiF9CO2++rjsiMUpR4h0m7UYxECycT4P-R4uEHDQ@mail.gmail.com> (raw)
In-Reply-To: <20120203231712.GA4095@x220.globalsuite.net>

Hi Johan/Vinicius,

On Fri, Feb 3, 2012 at 7:17 PM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
> Hi Vinicius,
>
> On Fri, Feb 03, 2012, Vinicius Costa Gomes wrote:
>> If ReverseServiceDiscovery is enabled and we are connected to a LE
>> device, we should do a Primary Service Discovery, not a SDP discovery
>> (which doesn't even make sense).
>> ---
>>
>> This patch assumes that it makes sense to reuse the ReverseServiceDiscovery
>> functionality for LE devices.
>>
>>
>>  src/device.c |    9 +++++++--
>>  1 files changed, 7 insertions(+), 2 deletions(-)
>
> Applied. Thanks. (and yes, I do think it should be fine to "reverse
> discover" LE services).

I'm fine as well, but due to the current Core spec restrictions, It is
unlikely BlueZ will act as slave/acceptor to this to be triggered on
valid scenarios. Unless we add support for single mode LE adapters, or
by "infringing" current Core spec's restriction and allow LE
connection between dual mode devices for testing purposes.

Best Regards,
-- 
Anderson Lizardo
Instituto Nokia de Tecnologia - INdT
Manaus - Brazil

      reply	other threads:[~2012-02-04 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 23:06 [PATCH BlueZ] device: Fix doing sdp discovery for LE devices Vinicius Costa Gomes
2012-02-03 23:17 ` Johan Hedberg
2012-02-04 12:14   ` Anderson Lizardo [this message]

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=CAJdJm_OFcUNiF9CO2++rjsiMUpR4h0m7UYxECycT4P-R4uEHDQ@mail.gmail.com \
    --to=anderson.lizardo@openbossa.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=vinicius.gomes@openbossa.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).