From: Christian Eggers <ceggers@arri.de>
To: <linux-bluetooth@vger.kernel.org>
Cc: <frederic.danis@collabora.com>, <ceggers@arri.de>
Subject: [PATCH BlueZ v2 03/15] doc/qualification: gap-pts: fix GAP/SEC/SEM/BV-24-C test
Date: Mon, 2 Mar 2026 14:30:31 +0100 [thread overview]
Message-ID: <20260302134540.25540-4-ceggers@arri.de> (raw)
In-Reply-To: <20260302134540.25540-1-ceggers@arri.de>
The test complains if the characteristic is created with read,write
---
doc/qualification/gap-pts.rst | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/doc/qualification/gap-pts.rst b/doc/qualification/gap-pts.rst
index 287be6c3460d..6b42e3090655 100644
--- a/doc/qualification/gap-pts.rst
+++ b/doc/qualification/gap-pts.rst
@@ -955,7 +955,7 @@ for which we know the test passed.
| | | | | |
| | | | | - *yes* when asked if primary service |
| | | | | |
-| | | | | - [bluetooth]# gatt.register-characteristic 0xAAAA read,write |
+| | | | | - [bluetooth]# gatt.register-characteristic 0xAAAA read,secure-write |
| | | | | |
| | | | | - enter '1' when prompted |
| | | | | |
@@ -1917,11 +1917,13 @@ for which we know the test passed.
| | | | +-------------------------------------------------------------------------+
| | | | | On demand run in a first terminal: |
| | | | | |
-| | | | | - btgatt-client -d <bdaddr> |
+| | | | | - btgatt-client -d <pts_bdaddr> |
| | | | | |
-| | | | | Pair to PTS on demand |
+| | | | | On pairing request by PTS, run 'bluetoothctl' on 2nd terminal: |
| | | | | |
-| | | | | On demand run in a first terminal: |
+| | | | | - [bluetooth]# pair <pts_bdaddr> |
+| | | | | |
+| | | | | After PTS requested a disconnect, run in a first terminal: |
| | | | | |
| | | | | - 'sudo grep -A 1 LocalSignatureKey \ |
| | | | | /var/lib/bluetooth/<iut_bdaddr>/<pts_bdaddr>/info | grep -v \ |
--
2.51.0
next prev parent reply other threads:[~2026-03-02 13:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 13:30 [PATCH BlueZ v2 00/15] doc/qualification: Updates for TCRL pkg101 Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 01/15] doc/qualification: gap-pics: add footnote for TSPC_GAP_21_9 feature Christian Eggers
2026-03-02 15:15 ` doc/qualification: Updates for TCRL pkg101 bluez.test.bot
2026-03-02 13:30 ` [PATCH BlueZ v2 02/15] doc/qualification: gap-pts: fix GAP/SEC/CSIGN/* tests Christian Eggers
2026-03-02 13:30 ` Christian Eggers [this message]
2026-03-02 13:30 ` [PATCH BlueZ v2 04/15] doc/qualification: sm-pics: update capabilities in table 7b Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 05/15] doc/qualification: sm-pts: fix SM/PER/PKE/BI-03-C and BV-02-C tests Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 06/15] doc/qualification: sm-pts: fix SM/PER/SCPK/BI-03-C test Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 07/15] doc/qualification: sm-pts: add description for M/PER/PIS/BV-0[1-2]-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 08/15] doc/qualification: sm-pts: add description for SM/PER/KDU/BI-04-C test Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 09/15] doc/qualification: gatt-pts: add description for GATT/SR/GAW/BI-39-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 10/15] doc/qualification: gatt-pts: update description for GATT/SR/GAN/BV-01-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 11/15] doc/qualification: gatt-pts: add description for GATT/SR/GAN/BV-03-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 12/15] doc/qualification: gatt-pts: update description for GATT/SR/GAI/BV-01-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 13/15] doc/qualification: gatt-pts: add description for GATT/SR/GAI/BV-02-C Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 14/15] doc/qualification: l2cap-pts: remove redundant test documentation Christian Eggers
2026-03-02 13:30 ` [PATCH BlueZ v2 15/15] doc/qualification: l2cap-pts: add descriptions for LE CFC tests Christian Eggers
2026-03-02 20:20 ` [PATCH BlueZ v2 00/15] doc/qualification: Updates for TCRL pkg101 patchwork-bot+bluetooth
2026-03-03 10:18 ` Christian Eggers
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=20260302134540.25540-4-ceggers@arri.de \
--to=ceggers@arri.de \
--cc=frederic.danis@collabora.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