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/09/06 21:12:21 UTC

[jira] [Resolved] (MYNEWT-347) BLE Host - GAP update params request should fall back to L2CAP update procedure

     [ https://issues.apache.org/jira/browse/MYNEWT-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christopher Collins resolved MYNEWT-347.
----------------------------------------
    Resolution: Fixed

> 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: Improvement
>          Components: Nimble
>            Reporter: Christopher Collins
>            Assignee: Christopher Collins
>             Fix For: v1_0_0_beta1
>
>
> 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)