From: Szymon Janc <szymon.janc@tieto.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] android/README: Update information about GATT HAL support
Date: Tue, 10 Jun 2014 15:02:08 +0200 [thread overview]
Message-ID: <1491984.URZc1pCphU@uw000953> (raw)
In-Reply-To: <1402392729-29775-1-git-send-email-szymon.janc@tieto.com>
On Tuesday 10 of June 2014 11:32:09 Szymon Janc wrote:
> ---
> android/README | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/android/README b/android/README
> index 91fc545..435cf56 100644
> --- a/android/README
> +++ b/android/README
> @@ -222,9 +222,9 @@ Profile ID HAL header Status
> ---------------------------------------
> core bluetooth.h complete
> a2dp bt_av.h complete
> -gatt bt_gatt.h partial
> - bt_gatt_client.h partial
> - bt_gatt_server.h initial
> +gatt bt_gatt.h complete
> + bt_gatt_client.h complete
> + bt_gatt_server.h complete
> handsfree bt_hf.h complete
> hidhost bt_hh.h complete
> health bt_hl.h initial
> @@ -293,6 +293,14 @@ get_player_app_values_text_cb NULL JNI implementation
> set_player_app_value_cb NULL JNI implementation
>
>
> +HAL GATT
> +--------
> +
> +methods:
> +client->set_adv_data missing kernel support for vendor data
> +client->connect is_direct parameter is ignored
> +
> +
> Known Android issues
> ====================
>
> @@ -324,3 +332,4 @@ HFP Response and Hold AT+BTRH, +BTRH
> HFP In-band Ring Tone +BSIR
> AVRCP Player Settings HAL API present but not used
> AVRCP Browsing No HAL API
> +GATT Read multiple characteristics No HAL API
>
Applied.
--
Best regards,
Szymon Janc
prev parent reply other threads:[~2014-06-10 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 9:32 [PATCH] android/README: Update information about GATT HAL support Szymon Janc
2014-06-10 13:02 ` Szymon Janc [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=1491984.URZc1pCphU@uw000953 \
--to=szymon.janc@tieto.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