On 2019-11-15 23:23, Gix, Brian wrote: > Applied, Thanks > > On Thu, 2019-11-14 at 15:52 -0800, Inga Stotland wrote: > > This introduces a chain of callbacks to indicate whether mesh io > > is initialized and mesh network is ready to use. > > > > This fixes the reported situation when the receive callbacks > > were setup before the HCI was fully initialized. In other words, > > BT_HCI_CMD_LE_SET_SCAN_PARAMETERS was called before BT_HCI_CMD_RESET > > and, as the result, the callback issueing BT_HCI_CMD_LE_SET_SCAN_ENABLE > > command was not called. > > --- > > mesh/main.c | 42 ++++++++++++++++++++++++------------ > > mesh/mesh-io-api.h | 3 ++- > > mesh/mesh-io-generic.c | 48 +++++++++++++++++++++++++++++++----------- > > mesh/mesh-io.c | 5 +++-- > > mesh/mesh-io.h | 6 +++++- > > mesh/mesh.c | 33 ++++++++++++++++++++++++----- > > mesh/mesh.h | 5 ++++- > > 7 files changed, 107 insertions(+), 35 deletions(-) I have just tried this patch, and I confirm it fixes the RX issue after restarting the bluetooth-meshd daemon. Thanks! Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@xxxxxxxxxxx http://www.aurel32.net
