Files
bumble_fork/docs/mkdocs/src/transports/hci_socket.md
Gilles Boccon-Gibod c2959dadb4 formatting and linting automation
Squashed commits:
[cd479ba] formatting and linting automation
[7fbfabb] formatting and linting automation
[c4f9505] fix after rebase
[f506ad4] rename job
[441d517] update doc (+7 squashed commits)
[2e1b416] fix invoke and github action
[6ae5bb4] doc for git blame
[44b5461] add GitHub action
[b07474f] add docs
[4cd9a6f] more linter fixes
[db71901] wip
[540dc88] wip
2022-12-15 23:07:17 -08:00

769 B

HCI SOCKET TRANSPORT

An HCI Socket can send/receive HCI packets to/from a Bluetooth HCI controller managed by the host OS. This is only supported on some platforms (currently only tested on Linux).

!!! note This type of transport can only be used for virtual hosts, not virtual controllers

Moniker

The moniker for an HCI Socket transport is either just hci-socket (to use the default/first Bluetooth controller), or hci-socket:<index> where <index> is the 0-based index of a Bluetooth controller device.

!!! example hci-socket Use an HCI socket to the first Bluetooth controller (hci0 on Linux)

!!! tip "On Linux" See the Linux Platform page for details on how to use HCI sockets on Linux