From: "Collin R. Mulliner" <collin@betaversion.net>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] more sdp patches
Date: Thu, 01 Dec 2005 23:40:58 -0800 [thread overview]
Message-ID: <1133509258.15695.8.camel@panic> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Hi Marcel,
here is another patch for bluez-libs for sdp. I added:
int sdp_set_access_protos_attr(sdp_record_t *rec, const sdp_list_t
*proto, const uint16_t attr);
this is to add stuff like SDP_ATTR_ADD_PROTO_DESC_LIST, actually I
modified sdp_set_access_protos to take another parameter and made
sdp_set_access_protos do a call to sdp_set_access_protos_attr to keep
backward compatibility
... Collin
--
Collin R. Mulliner <collin@betaversion.net>
BETAVERSiON Systems [www.betaversion.net]
info/pgp: finger collin@betaversion.net
USS Enterprise Bumperstricker: Our other starship separates into 3
pieces!
[-- Attachment #2: bluez_libs_add_access_inc --]
[-- Type: text/plain, Size: 488 bytes --]
--- bluez-libs-2.22/include/sdp_lib.h 2005-10-29 16:04:28.000000000 -0700
+++ bluez-libs-2.22_new/include/sdp_lib.h 2005-12-01 22:54:36.000000000 -0800
@@ -172,6 +174,7 @@
* Set the access protocols of the record to those specified in proto
*/
int sdp_set_access_protos(sdp_record_t *rec, const sdp_list_t *proto);
+int sdp_set_access_protos_attr(sdp_record_t *rec, const sdp_list_t *proto, const uint16_t attr);
/*
* Get protocol port (i.e. PSM for L2CAP, Channel for RFCOMM)
[-- Attachment #3: bluez_libs_add_access_src --]
[-- Type: text/plain, Size: 709 bytes --]
--- bluez-libs-2.22/src/sdp.c 2005-10-29 16:04:28.000000000 -0700
+++ bluez-libs-2.22_new/src/sdp.c 2005-12-01 22:55:27.000000000 -0800
@@ -1742,6 +1772,11 @@
*/
int sdp_set_access_protos(sdp_record_t *rec, const sdp_list_t *ap)
{
+ return(sdp_set_access_protos_attr(rec, ap, SDP_ATTR_PROTO_DESC_LIST));
+}
+
+int sdp_set_access_protos_attr(sdp_record_t *rec, const sdp_list_t *ap, const uint16_t attr)
+{
const sdp_list_t *p;
sdp_data_t *protos = 0;
@@ -1749,7 +1784,7 @@
sdp_data_t *seq = access_proto_to_dataseq(rec, (sdp_list_t *)p->data);
protos = sdp_seq_append(protos, seq);
}
- sdp_attr_add(rec, SDP_ATTR_PROTO_DESC_LIST, protos);
+ sdp_attr_add(rec, attr, protos);
return 0;
}
next reply other threads:[~2005-12-02 7:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 7:40 Collin R. Mulliner [this message]
2005-12-02 19:47 ` [Bluez-devel] more sdp patches Marcel Holtmann
2005-12-02 23:07 ` Collin R. Mulliner
2005-12-03 5:15 ` Marcel Holtmann
2005-12-04 7:53 ` Collin R. Mulliner
2005-12-04 8:08 ` 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=1133509258.15695.8.camel@panic \
--to=collin@betaversion.net \
--cc=bluez-devel@lists.sourceforge.net \
/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).