You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@mynewt.apache.org by "Christopher Collins (JIRA)" <ji...@apache.org> on 2016/07/13 18:28:20 UTC
[jira] [Created] (MYNEWT-347) BLE Host - GAP update params request
should fall back to L2CAP update procedure
Christopher Collins created MYNEWT-347:
------------------------------------------
Summary: BLE Host - GAP update params request should fall back to L2CAP update procedure
Key: MYNEWT-347
URL: https://issues.apache.org/jira/browse/MYNEWT-347
Project: Mynewt
Issue Type: Bug
Components: Nimble
Reporter: Christopher Collins
Assignee: Christopher Collins
Currently, the GAP update parameters procedure only sends the LE connection update HCI command. This works if either of the following is true:
* The device is the master
* Both peers support the connection parameter update link layer procedure
If the device is a slave and the connection parameter update LL procedure is unsupported, the GAP procedure will fail. Rather than failing, the GAP code should initiate the L2CAP update procedure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)