From: Claudio Takahasi <claudio.takahasi@openbossa.org>
To: linux-bluetooth@vger.kernel.org
Cc: Claudio Takahasi <claudio.takahasi@openbossa.org>
Subject: [PATCH 1/5] TODO: Setup advertising parameters and data
Date: Mon, 3 Jan 2011 18:45:50 -0300 [thread overview]
Message-ID: <1294091154-7367-1-git-send-email-claudio.takahasi@openbossa.org> (raw)
---
TODO | 11 +++++++++++
1 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/TODO b/TODO
index 54fef16..6c5c58d 100644
--- a/TODO
+++ b/TODO
@@ -54,6 +54,17 @@ Low Energy
Priority: Medium
Complexity: C2
+- Implement a tool(or extend hciconfig) to setup the advertising parameters
+ and data. Extend hciconfig passing extra arguments when enabling the
+ advertises is not the right approach, it will be almost impossible to
+ address all arguments needed in an acceptable way. For testing, we need
+ a tool to change easily the AD Flags, the UUIDs and other data that can be
+ exported through the advertising data field. Suggestions: 1) extend hciconfig
+ passing a config file when enabling advertises; 2) write a ncurses based tool
+
+ Priority: Medium
+ Complexity: C2
+
- Device Name Characteristic is a GAP characteristic for Low Energy. This
characteristic shall be integrated/used in the discovery procedure. The
ideia is to report the value of this characteristic using DeviceFound signals.
--
1.7.3.4
next reply other threads:[~2011-01-03 21:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-03 21:45 Claudio Takahasi [this message]
2011-01-03 21:45 ` [PATCH 2/5] TODO: Remove characteristic discovery for non connectable devices Claudio Takahasi
2011-01-03 21:45 ` [PATCH 3/5] TODO: Rename glib-helper file to a more convenient name Claudio Takahasi
2011-01-03 21:45 ` [PATCH 4/5] TODO: Refactoring of gatt.c functions Claudio Takahasi
2011-01-03 21:45 ` [PATCH 5/5] TODO: Start Discover All Primary Services after SDP if necessary Claudio Takahasi
2011-01-05 12:12 ` [PATCH 1/5] TODO: Setup advertising parameters and data Johan Hedberg
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=1294091154-7367-1-git-send-email-claudio.takahasi@openbossa.org \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox