From: Arman Uguray <armansito@chromium.org>
To: linux-bluetooth@vger.kernel.org
Cc: Arman Uguray <armansito@chromium.org>
Subject: [PATCH 00/10] shared/att: Implement sending ATT protocol requests.
Date: Thu, 26 Jun 2014 16:14:07 -0700 [thread overview]
Message-ID: <1403824457-22461-1-git-send-email-armansito@chromium.org> (raw)
This patch set adds support for sending all remaining ATT protocol requests
via bt_att_send and handling of the corresponding response PDUs.
Implemented are:
- All outgoing ATT protocol requests.
- All incoming ATT protocol responses.
NOT implemented (and on the TODO list) are:
- Outgoing ATT protocol commands.
- Outgoing signed PDUs.
- Outgoing notifications/indications.
- Handling of incoming notifications/indications and outgoing confirmation.
- Handling of incoming ATT protocol requests and outgoing responses.
Arman Uguray (10):
shared/att: Implement outgoing "Find Information" request/response.
shared/att: Implement outgoing "Find By Type Value" request/response.
shared/att: Implement outgoing "Read By Type" request/response.
shared/att: Implement outgoing "Read" request/response.
shared/att: Implement outgoing "Read Blob" request/response.
shared/att: Implement outgoing "Read Multiple" request/response.
shared/att: Implement outgoing "Read By Group Type" request/response.
shared/att: Implement outgoing "Write" request/response.
shared/att: Implement outgoing "Prepare Write" request/response.
shared/att: Implement outgoing "Execute Write" request/response.
src/shared/att-types.h | 16 +-
src/shared/att.c | 551 +++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 559 insertions(+), 8 deletions(-)
--
2.0.0.526.g5318336
next reply other threads:[~2014-06-26 23:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 23:14 Arman Uguray [this message]
2014-06-26 23:14 ` [PATCH 01/10] shared/att: Implement outgoing "Find Information" request/response Arman Uguray
2014-07-07 7:20 ` Marcel Holtmann
2014-07-07 7:49 ` Szymon Janc
2014-07-07 8:44 ` Marcel Holtmann
2014-07-07 8:18 ` Arman Uguray
2014-07-07 8:42 ` Marcel Holtmann
2014-07-07 9:02 ` Arman Uguray
2014-07-07 9:48 ` Marcel Holtmann
2014-06-26 23:14 ` [PATCH 02/10] shared/att: Implement outgoing "Find By Type Value" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 03/10] shared/att: Implement outgoing "Read By Type" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 04/10] shared/att: Implement outgoing "Read" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 05/10] shared/att: Implement outgoing "Read Blob" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 06/10] shared/att: Implement outgoing "Read Multiple" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 07/10] shared/att: Implement outgoing "Read By Group Type" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 08/10] shared/att: Implement outgoing "Write" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 09/10] shared/att: Implement outgoing "Prepare Write" request/response Arman Uguray
2014-06-26 23:14 ` [PATCH 10/10] shared/att: Implement outgoing "Execute " Arman Uguray
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=1403824457-22461-1-git-send-email-armansito@chromium.org \
--to=armansito@chromium.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;
as well as URLs for NNTP newsgroup(s).