[
https://issues.apache.org/jira/browse/MYNEWT-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15468564#comment-15468564
]
ASF subversion and git services commented on MYNEWT-347:
--------------------------------------------------------
Commit f77bf7fcc18029dd8fc5c7ae380b40d6d3c67465 in incubator-mynewt-core's
branch refs/heads/master from [~ccollins476]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=f77bf7f
]
MYNEWT-347 BLE Host - GAP update; use L2CAP proc.
Prior to this change, the host did not failover to the L2CAP connection
parameter update procedure when the GAP update procedure failed.
Rather, it was up to the application to manually do that.
Now, if the host automatically performs the L2CAP procedure if all of
the following are true:
* We are the slave.
* Controller reports the following status code in its command
status event:
o Unknown HCI command (0x01).
* Controller reports the following status code in its LE connection
update complete event:
o Unsupported remote feature (0x1a).
In addition, there was some missing functionality that this commit fills
in:
* Timeouts for GAP update procedures (30 seconds).
* Report and delete outstanding L2CAP sig procedures when the
connection is broken.
> 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_rel
>
>
> 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)
