mirror of
https://github.com/thead-yocto-mirror/meta-openembedded
synced 2026-09-07 22:54:41 +02:00
5cd87e8d6c
The bluetooth.service runs bluetoothd to manage bluetooth devices, if present, in the system. By design, it should be running in either of two cases: 1. A userspace utility (e.g. networkmanager) has made a dbus request for bluetooth services provided by org.bluez. Even without this patch, the bluetooth.service gets run via dbus activation under the systmed aliased name 'dbus-org-bluez.service'. Perfect! 2. A bluetooth device is added to the system. When a bluetooth device is added, udev triggers the special systemd target, bluetooth.target intended to pull in any services needed for bluetooth linked under bluetooth.target.wants. Enable bluetooth.service so it gets linked under bluetooth.target.wants and bluetoothd gets started when a user adds a bluetooth device to the system. To be clear, this isn't forcing bluetooth to be running all the time--- only when either of #1 or #2 are true. Signed-off-by: Ash Charles <ashcharles@gmail.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
This layer depends on:
URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-oe][PATCH'
You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Main layer maintainer: Koen Kooi <koen@dominion.thruhere.net>
Martin Jansa <martin.jansa@gmail.com>