55f8ccadec
Revert to the previous used order for the bluetooth related
services. First, load the driver and then execute the bluetooth
daemon. This is needed for two reasons:
* The bluetooth daemon caches the MAC address. Loading the module before
ensures the daemon caches the correct MAC.
* The connectcore-demo server stops working if the bluetooth interface
is unavailable when the server launches. This order ensures the demo
works as expected.
This change also brings back the problem of the btnxpuart module unload
failure on reboot/suspend. The following commit adds a workaround for
the driver issue.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
|
||
|---|---|---|
| .. | ||
| bluez5 | ||
| bluez5-5.41 | ||
| bluez5-5.65 | ||
| bluez5-init | ||
| bluez5-init.bb | ||
| bluez5.inc | ||
| bluez5_5.41.bb | ||
| bluez5_5.41.bbappend | ||
| bluez5_5.65.bbappend | ||