From: Peter Krystad <pkrystad@codeaurora.org>
To: linux-bluetooth@vger.kernel.org
Cc: Peter Krystad <pkrystad@codeaurora.org>
Subject: [PATCH v2 hcidump 0/5] Add BT 3.0+HS parsing
Date: Wed, 2 Nov 2011 17:56:52 -0700 [thread overview]
Message-ID: <1320281817-359-1-git-send-email-pkrystad@codeaurora.org> (raw)
This patch adds parsing and display of BT 3.0+HS signaling
v2 - updates to match revised a2mp.h from bluez
Peter Krystad (5):
Add L2CAP Create/Move channel definitions
Add A2MP definitions
Add parsing of L2CAP Create/Move Channel signals
Add parsing of A2MP signals
Minor cleanup of indentation in output
lib/a2mp.h | 137 +++++++++++++++
lib/l2cap.h | 44 +++++
parser/hci.c | 15 +-
parser/l2cap.c | 495 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
parser/parser.h | 1 +
src/hcidump.c | 1 +
6 files changed, 688 insertions(+), 5 deletions(-)
create mode 100644 lib/a2mp.h
--
1.7.7
--
Peter Krystad
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
next reply other threads:[~2011-11-03 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 0:56 Peter Krystad [this message]
2011-11-03 0:56 ` [PATCH v2 hcidump 1/5] Add L2CAP Create/Move channel definitions Peter Krystad
2011-11-03 0:56 ` [PATCH v2 hcidump 2/5] Add A2MP definitions Peter Krystad
2011-11-03 0:56 ` [PATCH v2 hcidump 3/5] Add parsing of L2CAP Create/Move Channel signals Peter Krystad
2011-11-03 0:56 ` [PATCH v2 hcidump 4/5] Add parsing of A2MP signals Peter Krystad
2011-11-11 14:24 ` Andrei Emeltchenko
2011-11-03 0:56 ` [PATCH v2 hcidump 5/5] Minor cleanup of indentation in output Peter Krystad
2011-11-11 14:28 ` [PATCH v2 hcidump 0/5] Add BT 3.0+HS parsing Andrei Emeltchenko
2011-12-08 8:38 ` Andrei Emeltchenko
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=1320281817-359-1-git-send-email-pkrystad@codeaurora.org \
--to=pkrystad@codeaurora.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).