meta-digi/meta-digi-dey/recipes-connectivity/bluez/bluez5-init
Javier Viguera 55f8ccadec bluetooth-init: start driver load service before bluetooth daemon
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>
2024-09-27 14:02:34 +02:00
..
ccimx6 bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx6sbc bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx6ul bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx8m bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx8x bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
ccimx9 bluetooth-init: start driver load service before bluetooth daemon 2024-09-27 14:02:34 +02:00
use-mainline-bsp bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00
bluetooth-init.service bluez5: split init scripts and systemd service in a different recipe 2022-05-09 16:40:04 +02:00