From: Szymon Janc <szymon.janc@codecoup.pl>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH V2 00/10] Initial code for BTP client
Date: Thu, 14 Dec 2017 10:12:30 +0100 [thread overview]
Message-ID: <1622233.3RcYCl6drf@ix> (raw)
In-Reply-To: <20171208140348.30342-1-szymon.janc@codecoup.pl>
On Friday, 8 December 2017 15:03:39 CET Szymon Janc wrote:
> Hi,
>
> Changes in V2:
> - adapter index is simply mapped to queue length
> - added support for reseting (removing all bonding) adapter
> - fixes for issues reported by valgrind
>
>
> Cover letter from V1:
> This adds initial code for BTP client. BTP stands for Bluetooth Tester
> Protocol and aims at automated testing of BT stack. BTP is binary
> protocol and is already implemented in Zephyr Project. This adds
> similar client to BlueZ tree. BTP specification is available at [1].
>
> Notable thing about this serie is that it doesn't use glib, gdbus or
> utils from src/shared folder. Instead it makes use of Embedded Linux
> Library which is available at [2].
>
> Comments are welcome.
>
> BR
> Szymon Janc
>
> [1]
> https://github.com/zephyrproject-rtos/zephyr/blob/master/tests/bluetooth/te
> ster/btp_spec.txt [2] https://git.kernel.org/pub/scm/libs/ell/ell.git/
>
> Szymon Janc (10):
> shared/btp: Add initial code for library
> tools/btpclient: Add initial code
> shared/btp: Add definitions for GAP service
> tools/btpclient: Add initial support for GAP service
> tools/btpclient: Add initial support for read controller info command
> tools/btpclient: Get initial values for adapter setttings
> tools/btpclient: Add support for tracking mutable adapter settings
> tools/btpclient: Add support for configuring adapter settings
> tools/btpclient: Store devices per adapter
> tools/btpclient: Add support for reseting adapter
>
> .gitignore | 1 +
> Makefile.tools | 8 +
> configure.ac | 11 +
> src/shared/btp.c | 383 +++++++++++++++++++++++
> src/shared/btp.h | 320 ++++++++++++++++++++
> tools/btpclient.c | 884
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++ 6 files changed,
> 1607 insertions(+)
> create mode 100644 src/shared/btp.c
> create mode 100644 src/shared/btp.h
> create mode 100644 tools/btpclient.c
This serie is now applied.
--
pozdrawiam
Szymon Janc
prev parent reply other threads:[~2017-12-14 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 14:03 [PATCH V2 00/10] Initial code for BTP client Szymon Janc
2017-12-08 14:03 ` [PATCH V2 01/10] shared/btp: Add initial code for library Szymon Janc
2017-12-08 14:03 ` [PATCH V2 02/10] tools/btpclient: Add initial code Szymon Janc
2017-12-08 14:03 ` [PATCH V2 03/10] shared/btp: Add definitions for GAP service Szymon Janc
2017-12-08 14:03 ` [PATCH V2 04/10] tools/btpclient: Add initial support " Szymon Janc
2017-12-08 14:03 ` [PATCH V2 05/10] tools/btpclient: Add initial support for read controller info command Szymon Janc
2017-12-08 14:03 ` [PATCH V2 06/10] tools/btpclient: Get initial values for adapter setttings Szymon Janc
2017-12-08 14:03 ` [PATCH V2 07/10] tools/btpclient: Add support for tracking mutable adapter settings Szymon Janc
2017-12-08 14:03 ` [PATCH V2 08/10] tools/btpclient: Add support for configuring " Szymon Janc
2017-12-08 14:03 ` [PATCH V2 09/10] tools/btpclient: Store devices per adapter Szymon Janc
2017-12-14 9:12 ` 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=1622233.3RcYCl6drf@ix \
--to=szymon.janc@codecoup.pl \
--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;
as well as URLs for NNTP newsgroup(s).