Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2] android/README: Update with implementation status summary
Date: Wed, 12 Feb 2014 14:00:59 +0100	[thread overview]
Message-ID: <2902202.eLTXuOKvvK@leonov> (raw)
In-Reply-To: <1392115207-14297-1-git-send-email-szymon.janc@tieto.com>

Hi,

On Tuesday 11 of February 2014 11:40:07 Szymon Janc wrote:
> This will give a better overview of implemented features.
> ---
>  android/README | 38 +++++++++++++++++++++++++++++++++-----
>  1 file changed, 33 insertions(+), 5 deletions(-)
> 
> diff --git a/android/README b/android/README
> index e3c314f..b987dc9 100644
> --- a/android/README
> +++ b/android/README
> @@ -132,15 +132,43 @@ automatically on HAL library initialization. To
> deinitialize HAL library and stop daemon type 'bluetooth cleanup'. Type
> 'help' for more information. Tab completion is also supported.
> 
> +=====================
> +Implementation status
> +=====================
> +
> +Summary of HALs implementation status.
> +
> +complete    - implementation is feature complete and Android Framework is
> able +              to use it normally
> +partial     - implementation is in progress and not all required features
> are +              present, Android Framework is able to use some of
> features +initial     - only initial implementations is present, Android
> Framework is +              able to initialize but most likely not able to
> use it +not started - no implementation, Android Framework is not able to
> initialize it +
> +Profile ID    HAL header         Status
> +---------------------------------------
> +core          bluetooth.h        complete
> +a2dp          bt_av.h            complete
> +gatt          bt_gatt.h          not started
> +              bt_gatt_client.h   not started
> +              bt_gatt_server.h   not started
> +handsfree     bt_hf.h            initial
> +hidhost       bt_hh.h            complete
> +health        bt_hl.h            not started
> +pan           bt_pan.h           complete
> +avrcp         bt_rc.h            partial
> +socket        bt_sock.h          partial
> +
>  ===========================
>  Implementation shortcomings
>  ===========================
> 
> -It is possible that some of HAL functionality is missing implementation due
> to -reasons like feature feasibility or necessity for latest Android
> Framework. -This sections provides list of such deficiencies. Note that HAL
> library is -always expected to fully implement HAL API so missing
> implementation might -happen only in daemon.
> +It is possible that some of HAL functionality (although being marked as
> +complete) is missing implementation due to reasons like feature feasibility
> or +necessity for latest Android Framework. This sections provides list of
> such +deficiencies. Note that HAL library is always expected to fully
> implement HAL +API so missing implementation might happen only in daemon.
> 
>  HAL Bluetooth
>  =============

Pushed.

-- 
BR
Szymon Janc

      reply	other threads:[~2014-02-12 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 10:40 [PATCH v2] android/README: Update with implementation status summary Szymon Janc
2014-02-12 13:00 ` 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=2902202.eLTXuOKvvK@leonov \
    --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