[
https://issues.apache.org/jira/browse/MYNEWT-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15484887#comment-15484887
]
ASF subversion and git services commented on MYNEWT-386:
--------------------------------------------------------
Commit 840bb64710b0f576fd39f21ad9dcd62c6fcb322b in incubator-mynewt-core's
branch refs/heads/master from [~wes3]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-mynewt-core.git;h=840bb64
]
MYNEWT-386: Controller should always send connection complete event
The following changes were made to insure that the controller will
always send a connection complete event to the host. When either
a connection create command is sent or a start advertising command
is sent, the controller will attempt to allocate an event buffer
with which to send the connection complete event. If this fails,
the controller will return an error: BLE_ERR_MEM_CAPACITY. If
this succeeds, the controller will then be able to send the
connection complete event to the host.
> Controller should always be able to send the connection complete event
> ----------------------------------------------------------------------
>
> Key: MYNEWT-386
> URL: https://issues.apache.org/jira/browse/MYNEWT-386
> Project: Mynewt
> Issue Type: Bug
> Components: Nimble
> Affects Versions: v0_9_0
> Reporter: William San Filippo
> Assignee: William San Filippo
> Fix For: v1_0_0_beta1
>
>
> The current nimble controller implementation does not guarantee that a
> connection complete event will be sent when a connection is established. The
> controller should guarantee that an event will be sent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
