c7adf015f9
Some Bluetooth controllers may expose hci0 even when the firmware initialization has not completed correctly. In that state, the init script may report success but bluetoothd cannot use the controller. Validate the controller through the kernel management interface before accepting the initialization as successful. This matches the interface used by bluetoothd and catches controllers that are visible through HCI but not registered in MGMT yet. Use a timeout for the MGMT query so a broken controller state cannot block the init script instead of falling back to the retry loop. https://onedigi.atlassian.net/browse/DEL-9512 Signed-off-by: Isaac Hermida <isaac.hermida@digi.com> |
||
|---|---|---|
| .. | ||
| bluez5 | ||
| bluez5-5.41 | ||
| bluez5-5.72 | ||
| bluez5-init | ||
| bluez5-init.bb | ||
| bluez5.inc | ||
| bluez5_5.41.bb | ||
| bluez5_5.41.bbappend | ||
| bluez5_5.72.bbappend | ||