aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-connectivity/bluez/bluez4_4.101.bb
AgeCommit message (Collapse)Author
2016-06-23Revert "python-pygobject, python-cloudeebus, python-dbusmock: Blacklist ↵Hongxu Jia
because of python-pygobject is broken" This reverts commit b0fae32dfc447ef9864e077d05c51bbbf763565b. Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-06-13python-pygobject, python-cloudeebus, python-dbusmock: Blacklist because of ↵Martin Jansa
python-pygobject is broken Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2016-03-14bluez4: use real introspection instead of legacy pygobjectAlexander Kanavin
Now that the real introspection is available, and legacy pygobject is not, the patch to use the latter should be removed. Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
2015-08-18bluez4: Allow systemd to activate bluetoothAsh Charles
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>
2015-05-11*obex*, navit, libsyncml, foxtrotgps, gypsy, bluez-hcidump, bluez4, ↵Martin Jansa
gst-plugin-bluetooth, gnome-bluetooth: blacklist bluez4 only recipes when bluez5 is in DISTRO_FEATURES foo
2015-05-11bluez collection: add (moved from oe-core)Cristian Iorga
BlueZ 4.x Bluetooth stack has been removed from oe-core. However, it is still supported, so add it to recipes-connectivity in meta-oe. meta-systemd layer bluez4 bbappend has been integrated into bluez4 recipe. In order to use it in oe-core/poky/YP, 'bluez5' backfill distro feature needs to be disabled via: DISTRO_FEATURES_BACKFILL_CONSIDERED = "bluez5" . 'bluetooth' distro feature needs to be present also. Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>