From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCH BlueZ] tools: add GoepL2capPsm decoding support to sdptool
Date: Mon, 6 Feb 2012 15:19:01 +0200 [thread overview]
Message-ID: <1328534341-11335-1-git-send-email-luiz.dentz@gmail.com> (raw)
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
---
tools/sdptool.c | 11 +++++++++--
1 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/tools/sdptool.c b/tools/sdptool.c
index aea4954..1a89245 100644
--- a/tools/sdptool.c
+++ b/tools/sdptool.c
@@ -226,6 +226,11 @@ static struct attrib_def audio_attrib_names[] = {
{ 0x302, "Remote audio volume control", NULL, 0 },
};
+/* Name of the various GOEP attributes. See BT assigned numbers */
+static struct attrib_def goep_attrib_names[] = {
+ { 0x200, "GoepL2capPsm", NULL, 0 },
+};
+
/* Same for the UUIDs. See BT assigned numbers */
static struct uuid_def uuid16_names[] = {
/* -- Protocols -- */
@@ -261,8 +266,10 @@ static struct uuid_def uuid16_names[] = {
{ 0x1102, "LANAccessUsingPPP", NULL, 0 },
{ 0x1103, "DialupNetworking (DUN)", NULL, 0 },
{ 0x1104, "IrMCSync", NULL, 0 },
- { 0x1105, "OBEXObjectPush", NULL, 0 },
- { 0x1106, "OBEXFileTransfer", NULL, 0 },
+ { 0x1105, "OBEXObjectPush",
+ goep_attrib_names, sizeof(goep_attrib_names)/sizeof(struct attrib_def) },
+ { 0x1106, "OBEXFileTransfer",
+ goep_attrib_names, sizeof(goep_attrib_names)/sizeof(struct attrib_def) },
{ 0x1107, "IrMCSyncCommand", NULL, 0 },
{ 0x1108, "Headset",
audio_attrib_names, sizeof(audio_attrib_names)/sizeof(struct attrib_def) },
--
1.7.7.6
next reply other threads:[~2012-02-06 13:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 13:19 Luiz Augusto von Dentz [this message]
2012-02-07 10:36 ` [PATCH BlueZ] tools: add GoepL2capPsm decoding support to sdptool 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=1328534341-11335-1-git-send-email-luiz.dentz@gmail.com \
--to=luiz.dentz@gmail.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).