Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Cc: linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] android/README: Update with implementation status summary
Date: Mon, 10 Feb 2014 15:53:37 +0100	[thread overview]
Message-ID: <116033164.PgDJ7QB7EE@leonov> (raw)
In-Reply-To: <CAF3PWx0fcUUQtdvm2c4m985vDNMdtOQKjKaFeg9L-LOZ+-dcxA@mail.gmail.com>

Hi Andrzej,

On Monday 10 of February 2014 15:35:15 Andrzej Kaczmarek wrote:
> Hi Szymon,
> 
> On 10 February 2014 12:50, Szymon Janc <szymon.janc@tieto.com> wrote:
> > This will give a better overview of implemented features.
> > ---
> > 
> >  android/README | 37 ++++++++++++++++++++++++++++++++-----
> >  1 file changed, 32 insertions(+), 5 deletions(-)
> > 
> > diff --git a/android/README b/android/README
> > index e3c314f..49536e2 100644
> > --- a/android/README
> > +++ b/android/README
> > @@ -132,15 +132,42 @@ 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          complete
> 
> This should be 'partial' since you application cannot register server
> on custom UUID with channel being assigned dynamically
> (BluetoothAdapter::listenUsingRfcommWithServiceRecord). I have patches
> which add this support but need to fix other code first in order to
> make them work properly.

Right, I'll send V2 later (unless you manage to socket send fixes before me:))

-- 
BR
Szymon Janc

  reply	other threads:[~2014-02-10 14:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 11:50 [PATCH] android/README: Update with implementation status summary Szymon Janc
2014-02-10 14:35 ` Andrzej Kaczmarek
2014-02-10 14:53   ` Szymon Janc [this message]
2014-02-10 18:37 ` 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=116033164.PgDJ7QB7EE@leonov \
    --to=szymon.janc@tieto.com \
    --cc=andrzej.kaczmarek@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