summaryrefslogtreecommitdiff
path: root/src/bluetooth/doc/src/bluetooth-index.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'src/bluetooth/doc/src/bluetooth-index.qdoc')
-rw-r--r--src/bluetooth/doc/src/bluetooth-index.qdoc17
1 files changed, 17 insertions, 0 deletions
diff --git a/src/bluetooth/doc/src/bluetooth-index.qdoc b/src/bluetooth/doc/src/bluetooth-index.qdoc
index 8f8bab4b..7f2a0315 100644
--- a/src/bluetooth/doc/src/bluetooth-index.qdoc
+++ b/src/bluetooth/doc/src/bluetooth-index.qdoc
@@ -80,6 +80,23 @@ or Qt was built without Qt D-Bus support.
The usage of the dummy backend is highlighted via an appropriate warning while building and running.
+\section3 Linux Specific
+
+Since Qt 6.5 the Linux peripheral support has two backend alternatives:
+BlueZ DBus and Bluetooth kernel API. The Bluez DBus backend introduced in Qt 6.5 is
+intended as the eventual successor of the lower abstraction level kernel backend.
+
+The BlueZ DBus API is more limited in terms of features and is therefore not
+the default backend for compatibility reasons.
+
+The BlueZ DBus backend can be configured to use by setting
+the \e QT_BLUETOOTH_USE_DBUS_PERIPHERAL environment variable. The QLowEnergyController
+peripheral instantiation then introspects the presence of BlueZ DBus peripheral APIs
+on the local bluetooth adapter. The minimum version requirement for BlueZ is 5.56.
+
+One noteworthy difference is that with BlueZ DBus peripheral backend the user process no longer
+needs to have the \e CAP_NET_ADMIN capability (eg. run as root).
+
\section3 \macos Specific
The Bluetooth API on \macos requires a certain type of event dispatcher
that in Qt causes a dependency to \l QGuiApplication. However, you can set the