linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Iain Hibbert <plunky@rya-online.net>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [patch] bluez-hcidump fix SDP universal attributes
Date: Tue, 19 Jan 2010 11:41:52 +0000 (GMT)	[thread overview]
Message-ID: <1263901312.199442.295.nullmailer@galant.ukfsn.org> (raw)
In-Reply-To: <1259610176.010210.13279.nullmailer@galant.ukfsn.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 766 bytes --]

On Mon, 30 Nov 2009, Iain Hibbert wrote:

> hcidump shows SDP universal attribute 0x000d as IconURL but in fact it is
> defined as "Additional Protocol Descriptor Lists". IconURL is 0x000c and I
> don't know what Icon_10 was, perhaps an older name?
>
> Eg, from an SDP probe of a mouse:
>
>       aid 0x000d (IconURL)
>          < < < uuid-16 0x0100 (L2CAP) uint 0x13 > < uuid-16 0x0011 (HIDP) > > >

Reposting because there was no response to this, patch is attached..

See "5.1.6 AdditionalProtocolDescriptorList attribute" and "5.1.14 IconURL
Attribute" sections in the core specification for reference..

(they sometimes call it AdditionalProtocolDescriptorLists and that is more
accurate as more than one protocol descriptor list may be included)

regards,
iain

[-- Attachment #2: fix SDP universal attributes for bluez-hcidump --]
[-- Type: TEXT/PLAIN, Size: 1570 bytes --]

--- parser/sdp.c.orig	2009-11-30 19:29:31.000000000 +0000
+++ parser/sdp.c
@@ -194,8 +194,8 @@ static sdp_attr_id_nam_lookup_table_t sd
 	{ SDP_ATTR_ID_BLUETOOTH_PROFILE_DESCRIPTOR_LIST, "BTProfileDescList"  },
 	{ SDP_ATTR_ID_DOCUMENTATION_URL,                 "DocURL"             },
 	{ SDP_ATTR_ID_CLIENT_EXECUTABLE_URL,             "ClientExeURL"       },
-	{ SDP_ATTR_ID_ICON_10,                           "Icon10"             },
 	{ SDP_ATTR_ID_ICON_URL,                          "IconURL"            },
+	{ SDP_ATTR_ID_ADDITIONAL_PROTOCOL_DESC_LISTS,    "AdditionalProtocolDescLists" },
 	{ SDP_ATTR_ID_SERVICE_NAME,                      "SrvName"            },
 	{ SDP_ATTR_ID_SERVICE_DESCRIPTION,               "SrvDesc"            },
 	{ SDP_ATTR_ID_PROVIDER_NAME,                     "ProviderName"       },
--- parser/sdp.h.orig	2009-11-30 19:29:35.000000000 +0000
+++ parser/sdp.h
@@ -129,8 +129,8 @@
 #define SDP_ATTR_ID_BLUETOOTH_PROFILE_DESCRIPTOR_LIST  0x0009
 #define SDP_ATTR_ID_DOCUMENTATION_URL                  0x000A
 #define SDP_ATTR_ID_CLIENT_EXECUTABLE_URL              0x000B
-#define SDP_ATTR_ID_ICON_10                            0x000C
-#define SDP_ATTR_ID_ICON_URL                           0x000D
+#define SDP_ATTR_ID_ICON_URL                           0x000C
+#define SDP_ATTR_ID_ADDITIONAL_PROTOCOL_DESC_LISTS     0x000D
 #define SDP_ATTR_ID_SERVICE_NAME                       0x0100
 #define SDP_ATTR_ID_SERVICE_DESCRIPTION                0x0101
 #define SDP_ATTR_ID_PROVIDER_NAME                      0x0102

  reply	other threads:[~2010-01-19 11:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 19:42 [patch] bluez-hcidump fix SDP universal attributes Iain Hibbert
2010-01-19 11:41 ` Iain Hibbert [this message]
2010-02-16  9:25   ` [PATCH] " Iain Hibbert
2010-02-16 15:42     ` Marcel Holtmann
2010-02-16 22:55       ` Iain Hibbert
2010-02-17 10:02         ` Marcel Holtmann
2010-02-17 10:32           ` Iain Hibbert
2010-02-17 17:19             ` 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=1263901312.199442.295.nullmailer@galant.ukfsn.org \
    --to=plunky@rya-online.net \
    --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).