bluetooth: bring interface up before launching bluetoothd
If the bluetoothd daemon is launched before the interface is ready RFCOMM/L2CAP listening socket connections fail (apparently because the channel is not ready) with BlueZ 5. Signed-off-by: Hector Palacios <hector.palacios@digi.com> https://jira.digi.com/browse/DEL-2042
This commit is contained in:
parent
dbeab04bcf
commit
a10e2a774a
|
|
@ -94,8 +94,8 @@ bt_init() {
|
||||||
fi
|
fi
|
||||||
}
|
}
|
||||||
|
|
||||||
echo "Starting bluetooth services."
|
|
||||||
start-stop-daemon -S --background --exec /usr/lib/bluez5/bluetooth/bluetoothd
|
|
||||||
|
|
||||||
# Check if this hardware does support Bluetooth
|
# Check if this hardware does support Bluetooth
|
||||||
[ -d "/proc/device-tree/bluetooth" ] && bt_init
|
[ -d "/proc/device-tree/bluetooth" ] && bt_init
|
||||||
|
|
||||||
|
echo "Starting bluetooth services."
|
||||||
|
start-stop-daemon -S --background --exec /usr/lib/bluez5/bluetooth/bluetoothd
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue