All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Grandel <fgrandel@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Lukasz Rymanowski <lukasz.rymanowski@tieto.com>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Szymon Janc <Szymon.Janc@tieto.com>,
	BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Peripheral role support for android
Date: Mon, 20 Jul 2015 00:42:45 +0200	[thread overview]
Message-ID: <55AC27E5.5010509@gmail.com> (raw)
In-Reply-To: <650B748F-76F8-4031-9397-E65D18AD01A4@holtmann.org>

Hi guys,

just a quick update from my side so that you know, I'm still active.

Done:
1) kernel backports: provide patches necessary to support the current 
linux-next master
2) android/bluetooth: implement bt_le_read_adv_features() to retrieve 
num supported instances from the kernel
3) android/bluetooth: change prepare_le_features() to retrieve the max 
number of adv instances from the kernel and save it to the adapter 
struct - will use bt_le_read_adv_features()
4) android/gatt: change [un]register_app() to correctly manage app ids 
(aka instance ids) in the permitted range including appropriate error 
handling when the max number of instances is reached
5) android/bluetooth: implement bt_le_{add|remove}_advertising() to 
support the new multi-adv features in the kernel
6) android/gatt: implement the handle*multi_adv*() methods using 
bt_le_{add|remove}_advertising()

Currently working on:
7) android/tester-{bluetooth|gatt}: write supporting tests

Florian

      parent reply	other threads:[~2015-07-19 22:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-27  0:05 Peripheral role support for android Florian Grandel
2015-06-29 13:52 ` Marcel Holtmann
2015-07-01 13:39   ` Florian Grandel
2015-07-19 22:42   ` Florian Grandel [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=55AC27E5.5010509@gmail.com \
    --to=fgrandel@gmail.com \
    --cc=Szymon.Janc@tieto.com \
    --cc=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=lukasz.rymanowski@tieto.com \
    --cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.