When initially calling service bluetooth start ubt0, I usually get an error:
/etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0
When tracking the error down, I can link it to the command
ngctl mkpeer ubt0: hci hook drv
ngctl: send msg: File exists
So I assume, when attaching my usb host controller, the usb framework
has already launched the bluetooth start ubt0? Is that correct?
What happens then is that
bluetooth_shutdown_stack $dev
is called, actually shutting down the device. This is exactly the
opposite of the expected effect.
Maybe the rc script should check if the stack is already set up and exit
with a more verbose error and then not shut down the interface?
erdgeist
_______________________________________________
freebsd-bluetooth@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "freebsd-bluetooth-unsubscr...@freebsd.org"
