From 6bff733c7300da955a240c6905e75a0e48d4b737 Mon Sep 17 00:00:00 2001 From: Matthias Ringwald Date: Thu, 16 Apr 2015 12:41:33 +0200 Subject: [PATCH] manual: mention hci fragmentation --- docs/manual/protocols_profiles.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/protocols_profiles.tex b/docs/manual/protocols_profiles.tex index 5666ff0a0..9996a96f0 100644 --- a/docs/manual/protocols_profiles.tex +++ b/docs/manual/protocols_profiles.tex @@ -45,7 +45,7 @@ In the following, we first explain how the various Bluetooth protocols are used \subsection{HCI - Host Controller Interface} -The HCI protocol provides a command interface to the Bluetooth chipset. In BTstack, the HCI implementation also keeps track of all active connections and handles the re-assembly of higher layer (L2CAP) packets. +The HCI protocol provides a command interface to the Bluetooth chipset. In BTstack, the HCI implementation also keeps track of all active connections and handles the fragmentation and re-assembly of higher layer (L2CAP) packets. Please note, that an application rarely has to send HCI commands on its own. Instead, BTstack provides convenience functions in GAP and higher level protocols use HCI automatically. E.g. to set the name, you can call \emph{gap\_set\_local\_name()} before powering up. The main use of HCI commands in application is during the startup phase to configure special features that are not available via the GAP API yet.