From: Nick Pelly <npelly@google.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Set OPUSH SDP record supported format list to 0xff (any object type).
Date: Wed, 3 Feb 2010 11:23:03 -0800 [thread overview]
Message-ID: <35c90d961002031123o7bf0ad95o420810d194090189@mail.gmail.com> (raw)
In-Reply-To: <1265224887-48653-1-git-send-email-npelly@google.com>
(Second patch removes signed-off line as per userspace bluez requirements)
On Wed, Feb 3, 2010 at 11:21 AM, Nick Pelly <npelly@google.com> wrote:
> This fixed an issue with sending an image from OSX. OSX would show a warning
> that the bluez stack does not support this file type, but offer to send it
> anyway (which works). This change to advertise support for all object types
> will remove this warning.
>
> The list of file types that can be advertised in the SDP record is very limited
> anyway. It is best to list that we support all file types here, and then filter
> at the OPP/OBEX connection instead.
>
> For reference:
> 0x01 = vCard 2.1
> 0x02 = vCard 3.0
> 0x03 = vCal 1.0
> 0x04 = iCal 2.0
> 0x05 = vNote
> 0x06 = vMessage
> 0xFF = any type of object.
> ---
> tools/sdptool.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/tools/sdptool.c b/tools/sdptool.c
> index 5a199a9..bc2dc61 100644
> --- a/tools/sdptool.c
> +++ b/tools/sdptool.c
> @@ -1751,8 +1751,7 @@ static int add_opush(sdp_session_t *session, svc_info_t *si)
> sdp_record_t record;
> uint8_t chan = si->channel ? si->channel : 9;
> sdp_data_t *channel;
> - uint8_t formats[] = { 0x01, 0x02, 0x03, 0x04, 0x05, 0x06 };
> - //uint8_t formats[] = { 0xff };
> + uint8_t formats[] = { 0xff };
> void *dtds[sizeof(formats)], *values[sizeof(formats)];
> unsigned int i;
> uint8_t dtd = SDP_UINT8;
> --
> 1.6.5.3
>
>
next prev parent reply other threads:[~2010-02-03 19:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 19:21 [PATCH] Set OPUSH SDP record supported format list to 0xff (any object type) Nick Pelly
2010-02-03 19:23 ` Nick Pelly [this message]
2010-02-05 1:12 ` Johan Hedberg
-- strict thread matches above, loose matches on Subject: below --
2010-02-03 19:15 Nick Pelly
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=35c90d961002031123o7bf0ad95o420810d194090189@mail.gmail.com \
--to=npelly@google.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