From: Antti Julku <antti.julku@nokia.com>
To: linux-bluetooth@vger.kernel.org
Subject: Name resolution for mgmt interface
Date: Fri, 09 Sep 2011 17:36:44 +0300 [thread overview]
Message-ID: <4E6A247C.5040403@nokia.com> (raw)
Hello Bluetooth experts,
Name resolution of older devices not supporting EIR is still missing
from the management interface. I discussed with Johan, and he suggested
the following architecture (if I understood correctly):
New command and event are added to mgmt interface:
* Unknown Names Event
* Resolve Names Command
When device discovery is completed, kernel sends list of BT addresses of
devices which names are unknown (no name in EIR data) with Unknown Names
Event.
User space can then request name resolving with Resolve Names Command,
which takes list of BT addresses as parameter. User space gets a Remote
Name Event for each device.
Internally kernel would have a list of found devices, to which devices
are added during discovery. Device in the list is flagged as unknown
unless there was name for it in EIR data. After discovery is completed,
event with list of unknown devices is sent, and the found devices list
is cleared (it's valid only during one discovery session).
Not sure if name resolution should be included in the discovery session
done via mgmt interface (while Discovering Event indicates discovery is
ongoing), and how to track discovery state in that case. Maybe another
state is needed in hdev->flags (e.g. HCI_DISCOVERY) if HCI_INQUIRY is
not enough?
Any opinions? I think it would be good to have wider discussion before
making patches.
Br,
Antti
next reply other threads:[~2011-09-09 14:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-09 14:36 Antti Julku [this message]
2011-09-09 22:19 ` Name resolution for mgmt interface Claudio Takahasi
2011-09-10 6:23 ` Marcel Holtmann
2011-09-12 16:56 ` Claudio Takahasi
2011-09-12 19:07 ` Marcel Holtmann
2011-09-12 19:15 ` tim.howes
2011-09-13 7:55 ` Luiz Augusto von Dentz
2011-09-13 6:39 ` Antti Julku
2011-09-13 8:48 ` Marcel Holtmann
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=4E6A247C.5040403@nokia.com \
--to=antti.julku@nokia.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).