Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 2/2] Bluetooth: Add mgmt_remote_name event
Date: Wed, 30 Mar 2011 17:00:42 +0300	[thread overview]
Message-ID: <20110330140042.GA28881@jh-x301> (raw)
In-Reply-To: <AANLkTi=BZhjKvCBon7qhS0tCPkABmv7to39UhoaQE1a8@mail.gmail.com>

Hi,

On Wed, Mar 30, 2011, Anderson Lizardo wrote:
> > This patch adds a new remote_name event to the Management interface
> > which is sent every time the name of a remote device is resolved (over
> > BR/EDR).
> 
> Just wondering if we could ever reuse this for LE. For LE (and GATT
> over BR/EDR ?), I believe the "remote device name resolution" is done
> by looking at the GAP "Device Name" characteristic after a service
> discovery (see spec page 1739).
> 
> The advertising data may contain the "full" device name as well, but
> it is not mandatory to include it. GAP Device Name OTOH is mandatory.

I suppose it can't be reused for LE. Btw, this event will *not* be sent
for advertising data or extended inquiry response data containing a
remote name. User space is expected to do that extraction from the data
(which comes in the mgmt_device_found event).

Johan

  reply	other threads:[~2011-03-30 14:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 10:18 [PATCH 1/2] Bluetooth: Add mgmt_device_found event johan.hedberg
2011-03-30 10:18 ` [PATCH 2/2] Bluetooth: Add mgmt_remote_name event johan.hedberg
2011-03-30 13:51   ` Anderson Lizardo
2011-03-30 14:00     ` Johan Hedberg [this message]
2011-03-30 12:30 ` [PATCH 1/2] Bluetooth: Add mgmt_device_found event Anderson Lizardo
2011-03-30 20:57   ` [PATCH 1/2 v2] " johan.hedberg
2011-04-04 21:49     ` Gustavo F. Padovan

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=20110330140042.GA28881@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=anderson.lizardo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox