public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nick Pelly" <npelly@google.com>
To: linux-bluetooth@vger.kernel.org
Cc: "Nick Pelly" <npelly@google.com>
Subject: Re: [PATCH] Advertise telephony service class for handsfree AG role, for Nokia 616 support.
Date: Tue, 23 Sep 2008 11:29:47 -0700	[thread overview]
Message-ID: <35c90d960809231129q427ce8capd4d50818dfcd2225@mail.gmail.com> (raw)
In-Reply-To: <1222194344-27949-1-git-send-email-npelly@google.com>

The first patch used HANDSFREE_SVCLASS_ID - wrong. Please use the
second patch. Sorry about that.

On Tue, Sep 23, 2008 at 11:25 AM, Nick Pelly <npelly@google.com> wrote:
> The Nokia 616 incorrectly requires the telehony bit to be set to make a
> handsfree connection.
> ---
>  src/sdpd-service.c |    7 +++++++
>  1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/src/sdpd-service.c b/src/sdpd-service.c
> index 30aad32..12c999c 100644
> --- a/src/sdpd-service.c
> +++ b/src/sdpd-service.c
> @@ -121,6 +121,13 @@ static void update_svclass_list(void)
>                case HANDSFREE_SVCLASS_ID:
>                        val |= 0x20;    /* Audio */
>                        break;
> +               /* For Nokia 616 carkit compatability - it incorrectly requires
> +                * the telephony bit set on the HFP AG, despite this not
> +                * being a requirement of the handsfree spec.
> +                */
> +               case HANDSFREE_AGW_SVCLASS_ID:
> +                       val |= 0x40;    /* Telephony */
> +                       break;
>                case CORDLESS_TELEPHONY_SVCLASS_ID:
>                case INTERCOM_SVCLASS_ID:
>                case FAX_SVCLASS_ID:
> --
> 1.5.5
>
>

      reply	other threads:[~2008-09-23 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 18:19 [PATCH] Advertise telephony service class for handsfree AG role, for Nokia 616 support Nick Pelly
2008-09-23 18:25 ` Nick Pelly
2008-09-23 18:29   ` Nick Pelly [this message]

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=35c90d960809231129q427ce8capd4d50818dfcd2225@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