Running Quirky, there was no Bluetooth controller found. After some research, and looking at Raspbian, I discovered a udev rule is required, and from systemd I found that 'hciattach' has to be run. Then I found that extra firmware is required.
So far, have got the controller working, or at least responding.
Comments:Bluetooth hciattach Posted on 18 Sep 2016, 19:06 by admin
Correction, the advise at the Alpine Linux site is probably complete, the udev rule 99-com.rules is probably not needed.
This is because Raspbian does this:
/usr/bin/hciattach /dev/serial1 bcm43xx 921600 noflow -
Where the udev rule creates a symlink of /dev/serial1 to /dev/ttyAMA0
Whereas, Alpine just does this:
hciattach /dev/ttyAMA0 bcm43xx 115200 noflow -
...interesting difference in the speed.
Bluetooth setup on Pi Posted on 18 Sep 2016, 18:55 by admin
Some extra notes, for anyone reading this who is needing to do the same thing.
This info is useful:
What that doesn't explain though, is you also need /etc/udev/rules.d/99-com.rules (which can be edited to remove the group assignments).
This file is found in the Raspbian DEB 'raspberrypi-sys-mods'.
The systemd service that runs hciattach, as explained in the above link, is in Raspbian DEB 'pi-bluetooth'.