From: Alan Martinovic <alan.martinovic@senic.com>
To: linux-bluetooth@vger.kernel.org
Subject: Self qualification of BlueZ with LaunchStudio and Profile Tuning Suite (PTS)
Date: Tue, 14 Nov 2017 17:48:02 +0100 [thread overview]
Message-ID: <CAOT_U5bHPVAfQsuNqsgD-i=UnNAXp5n981FTqWmuDgC-escT+A@mail.gmail.com> (raw)
It seems like PTS can do the testing automatically with the DUT, a
dongle from BTSIG (https://bluetoothstore.org/) and the right test
description from Launch Studio
(https://www.bluetooth.com/develop-with-bluetooth/test-tools/profile-tuning-suite).
If anyone self qualified the BlueZ host on a product using this
method, could she/he please share the steps and experiences?
How does one work out what elements of the BT standards are required
in the product?
(to know what to include in the ICS)
Is it sufficient to say:
"We want to be a Central device that connects to Peripherals, and
interprets GATT commands" and based on that select "Central" and
"GATT" in the Launch Studio project, and fix all
conflicts/dependencies in the ICS generation step?
Be Well,
Alan
reply other threads:[~2017-11-14 16:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAOT_U5bHPVAfQsuNqsgD-i=UnNAXp5n981FTqWmuDgC-escT+A@mail.gmail.com' \
--to=alan.martinovic@senic.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;
as well as URLs for NNTP newsgroup(s).