From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] more sdp patches
Date: Fri, 02 Dec 2005 20:47:57 +0100 [thread overview]
Message-ID: <1133552877.24022.5.camel@blade> (raw)
In-Reply-To: <1133509258.15695.8.camel@panic>
Hi Collin,
> 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
this won't work, because the additional protocol descriptor list is a
sequence of sequence of sequence. Compare this from my HCRP capable
printer:
Attribute 0x0004 - ProtocolDescriptorList
Sequence
Sequence
UUID16 0x0100 - L2CAP
UINT16 0x1003
Sequence
UUID16 0x0012 - HardcopyControlChannel
Attribute 0x000d - AdditionalProtocolDescriptorLists
Sequence
Sequence
Sequence
UUID16 0x0100 - L2CAP
UINT16 0x1001
Sequence
UUID16 0x0014 - HardcopyDataChannel
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-02 19:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 7:40 [Bluez-devel] more sdp patches Collin R. Mulliner
2005-12-02 19:47 ` Marcel Holtmann [this message]
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=1133552877.24022.5.camel@blade \
--to=marcel@holtmann.org \
--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).