[
https://issues.apache.org/jira/browse/MYNEWT-726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15987760#comment-15987760
]
ASF subversion and git services commented on MYNEWT-726:
--------------------------------------------------------
Commit 46d67b04b26d25391d057785765549e5f72d04d0 in incubator-mynewt-core's
branch refs/heads/bluetooth5 from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=46d67b0
]
nimble/controller: MYNEWT-726
Modify how the controller deals with the terminate procedure. The
old method set a pending control procedure bit and it was not the
best way to deal with this since the terminate procedure can
occur while another control procedure is in process. The
new method uses a flag in the connection state machine flags
to denote that the terminate procedure was started. Started means
a control pdu was allocated and enqueued. The disconnect reason
being non-zero means that the connection is to be terminated.
> Modify how controller handles terminate control procedure
> ---------------------------------------------------------
>
> Key: MYNEWT-726
> URL: https://issues.apache.org/jira/browse/MYNEWT-726
> Project: Mynewt
> Issue Type: Improvement
> Components: Nimble
> Affects Versions: v1_0_0_rel
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_1_0_rel
>
> Attachments: ruuvitag_revb4_schema.pdf
>
>
> The terminate control procedure can occur while other control procedures are
> in process. The way the controller currently handles this causes some extra
> checks in the code and can be handled better.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
