From: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: [PATCHv5 18/19] android/socket: Add PBAP SDP record
Date: Tue, 19 Nov 2013 15:30:08 +0200 [thread overview]
Message-ID: <1384867809-18135-19-git-send-email-Andrei.Emeltchenko.news@gmail.com> (raw)
In-Reply-To: <1384867809-18135-1-git-send-email-Andrei.Emeltchenko.news@gmail.com>
From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
This adds SDP service record like shown below:
Service Name: OBEX Phonebook Access Server
Service RecHandle: 0x10002
Service Class ID List:
"Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
"RFCOMM" (0x0003)
Channel: 15
"OBEX" (0x0008)
Profile Descriptor List:
"Phonebook Access" (0x1130)
Version: 0x0100
---
android/socket.c | 65 +++++++++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 64 insertions(+), 1 deletion(-)
diff --git a/android/socket.c b/android/socket.c
index 9358d4a..0c71297 100644
--- a/android/socket.c
+++ b/android/socket.c
@@ -171,6 +171,67 @@ static sdp_record_t *create_opp_record(uint8_t chan)
return record;
}
+static sdp_record_t *create_pbap_record(uint8_t chan)
+{
+ sdp_list_t *svclass_id, *pfseq, *apseq, *root;
+ uuid_t root_uuid, pbap_uuid, rfcomm_uuid, obex_uuid;
+ sdp_profile_desc_t profile[1];
+ sdp_list_t *aproto, *proto[2];
+ sdp_data_t *channel;
+ uint8_t formats[] = { 0x01 };
+ uint8_t dtd = SDP_UINT8;
+ sdp_data_t *sflist;
+ sdp_record_t *record;
+
+ record = sdp_record_alloc();
+ if (!record)
+ return NULL;
+
+ record->handle = sdp_next_handle();
+
+ sdp_uuid16_create(&root_uuid, PUBLIC_BROWSE_GROUP);
+ root = sdp_list_append(NULL, &root_uuid);
+ sdp_set_browse_groups(record, root);
+
+ sdp_uuid16_create(&pbap_uuid, PBAP_PSE_SVCLASS_ID);
+ svclass_id = sdp_list_append(NULL, &pbap_uuid);
+ sdp_set_service_classes(record, svclass_id);
+
+ sdp_uuid16_create(&profile[0].uuid, PBAP_PROFILE_ID);
+ profile[0].version = 0x0100;
+ pfseq = sdp_list_append(NULL, profile);
+ sdp_set_profile_descs(record, pfseq);
+
+ sdp_uuid16_create(&rfcomm_uuid, RFCOMM_UUID);
+ proto[0] = sdp_list_append(NULL, &rfcomm_uuid);
+ channel = sdp_data_alloc(SDP_UINT8, &chan);
+ proto[0] = sdp_list_append(proto[0], channel);
+ apseq = sdp_list_append(NULL, proto[0]);
+
+ sdp_uuid16_create(&obex_uuid, OBEX_UUID);
+ proto[1] = sdp_list_append(NULL, &obex_uuid);
+ apseq = sdp_list_append(apseq, proto[1]);
+
+ aproto = sdp_list_append(NULL, apseq);
+ sdp_set_access_protos(record, aproto);
+
+ sflist = sdp_data_alloc(dtd, formats);
+ sdp_attr_add(record, SDP_ATTR_SUPPORTED_REPOSITORIES, sflist);
+
+ sdp_set_info_attr(record, "OBEX Phonebook Access Server", NULL, NULL);
+
+ sdp_data_free(channel);
+ sdp_list_free(proto[0], NULL);
+ sdp_list_free(proto[1], NULL);
+ sdp_list_free(apseq, NULL);
+ sdp_list_free(pfseq, NULL);
+ sdp_list_free(root, NULL);
+ sdp_list_free(svclass_id, NULL);
+ sdp_list_free(aproto, NULL);
+
+ return record;
+}
+
static struct profile_info {
uint8_t uuid[16];
uint8_t channel;
@@ -183,7 +244,9 @@ static struct profile_info {
0x00, 0x00, 0x11, 0x2F, 0x00, 0x00, 0x10, 0x00,
0x80, 0x00, 0x00, 0x80, 0x5F, 0x9B, 0x34, 0xFB
},
- .channel = PBAP_DEFAULT_CHANNEL
+ .channel = PBAP_DEFAULT_CHANNEL,
+ .svc_hint = SVC_HINT_OBEX,
+ .create_record = create_pbap_record
}, {
.uuid = {
0x00, 0x00, 0x11, 0x05, 0x00, 0x00, 0x10, 0x00,
--
1.7.10.4
next prev parent reply other threads:[~2013-11-19 13:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 13:29 [PATCHv5 00/19] Socket HAL Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 01/19] android/hal-sock: Print bdaddr string instead of pointer Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 02/19] android/socket: Add get RFCOMM default channel Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 03/19] android/socket: Define structs and implement listen Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 04/19] android/socket: Implement socket accepted event Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 05/19] android/socket: Implement Android RFCOMM stack events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 06/19] android/socket: Implement RFCOMM events Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 07/19] android/socket: Send accept signal to Android through hal_fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 08/19] android/socket: Write channel to Android fd Andrei Emeltchenko
2013-11-19 13:29 ` [PATCHv5 09/19] android/socket: Implement socket connect HAL method Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 10/19] android/socket: Parse SDP response and connect Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 11/19] android/socket: Implement HAL connect call Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 12/19] android/socket: Send RFCOMM channel to framework Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 13/19] android/socket: Send connect signal on connect Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 14/19] android/socket: Close file descriptor after sending Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 15/19] android/socket: Add SDP record for OPP profile Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 16/19] android/socket: Add MAS uuid to profile table Andrei Emeltchenko
2013-11-19 13:30 ` [PATCHv5 17/19] android/socket: Add SPP " Andrei Emeltchenko
2013-11-19 13:30 ` Andrei Emeltchenko [this message]
2013-11-19 13:30 ` [PATCHv5 19/19] android/socket: Add SPP SDP record 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=1384867809-18135-19-git-send-email-Andrei.Emeltchenko.news@gmail.com \
--to=andrei.emeltchenko.news@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).