facilitate start up without bluetooth controller

Add prefix '-' in the bluetooth service ExecStartPre
directive, to allow for errors: hciconfig will
return an error if there's no controller in the
system.

Bug-AGL: SPEC-3301
Signed-off-by: Raquel Medina <raquel.medina@konsulko.com>
Change-Id: Id4d5de549e73fe8f744681b33debd6043e1bc9ba
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/24952
Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
Reviewed-by: Scott Murray <scott.murray@konsulko.com>

diff --git a/meta-agl-profile-core/recipes-connectivity/bluez5/bluez5/bluetooth.service b/meta-agl-profile-core/recipes-connectivity/bluez5/bluez5/bluetooth.service
index e389e1a..8ae83bd 100644 (file)
--- a/meta-agl-profile-core/recipes-connectivity/bluez5/bluez5/bluetooth.service
+++ b/meta-agl-profile-core/recipes-connectivity/bluez5/bluez5/bluetooth.service
@@ -6,7 +6,7 @@ ConditionPathIsDirectory=/sys/class/bluetooth
 [Service]
 Type=dbus
 BusName=org.bluez
-ExecStartPre=/usr/bin/hciconfig hci0 aclmtu 930:10
+ExecStartPre=-/usr/bin/hciconfig hci0 aclmtu 930:10
 ExecStart=/usr/libexec/bluetooth/bluetoothd
 NotifyAccess=main
 #WatchdogSec=10