I have an AMD system with Sabertooth 990FX motherboard, running Kubuntu
12.04 and KDE 4.11.1. Chipset is AMD990FX/SB950, and audio spec is
Realtek ALC892 8-channel Hi Def audio. I have audio outputs connected to
the analog out ports, and digital coax out to a mini-card connected to
the
Some notes:
* This depends on 'androgenizer', a tool to generate Android-style
Android.mk files from an autotools build system.
* This assumes that PA is run as the system daemon and configures
accordingly.
* In the Android build, libltdl is likely not available when configure
is being
On Tue, 2013-09-24 at 19:45 -0300, jprv...@gmail.com wrote:
@@ -745,6 +748,15 @@ static void
parse_interfaces_and_properties(pa_bluetooth_discovery *y, DBusMessa
dbus_message_iter_next(element_i);
}
+PA_HASHMAP_FOREACH(d, y-devices, state)
+if (!d-adapter
On Tue, 2013-09-24 at 19:45 -0300, jprv...@gmail.com wrote:
diff --git a/src/modules/bluetooth/module-bluez5-device.c
b/src/modules/bluetooth/module-bluez5-device.c
index 36d7174..013cce5 100644
--- a/src/modules/bluetooth/module-bluez5-device.c
+++
Here are some small fixes to issues that I found while reviewing the
big Bluetooth patch set from João.
Tanu Kaskinen (5):
bluetooth: Remove adapter_remove_all()
bluetooth: Fix variable constness
bluetooth: Fix notifying about new devices
bluetooth: Remove device_remove_all()
bluetooth:
The string points to memory inside a DBusMessage, so we don't own the string.
---
src/modules/bluetooth/bluez5-util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/modules/bluetooth/bluez5-util.c
b/src/modules/bluetooth/bluez5-util.c
index 2be15d8..eaff4b1 100644
---
The function did two things: set device_info_valid to -1 and called
device_free() for each device in the hashmap. Setting
device_info_valid to -1 was unnecessary. The main purpose of that was
to fire DEVICE_CONNECTION_CHANGED as a side effect, but that hook is
fired anyway in device_free(), as a
Normally devices are created and their properties are parsed before
creating any transports for the device, and the
DEVICE_CONNECTION_CHANGED hook is fired when the first transport is
created. It's possible, however, that a transport is created before
the device that it belongs to, and in this
When parsing device properties, missing adapter will result in
device_info_valid being set to -1. It is then logical that if the
adapter goes missing at a later point, device_info_valid gets set to
-1.
---
src/modules/bluetooth/bluez5-util.c | 4 +++-
1 file changed, 3 insertions(+), 1
The function was redundant, because all it did was call adapter_free()
for each adapter in the hashmap, and that can be delegated to
pa_hashmap when freeing or emptying it.
---
src/modules/bluetooth/bluez5-util.c | 20
1 file changed, 4 insertions(+), 16 deletions(-)
diff
On Fri, 2013-09-20 at 17:27 +0530, Arun Raghavan wrote:
---
src/pulsecore/hashmap.h | 4
1 file changed, 4 insertions(+)
diff --git a/src/pulsecore/hashmap.h b/src/pulsecore/hashmap.h
index ae030ed..e42732a 100644
--- a/src/pulsecore/hashmap.h
+++ b/src/pulsecore/hashmap.h
@@ -85,6
Am 29.09.2013 14:22, schrieb Arun Raghavan:
Some notes:
* This depends on 'androgenizer', a tool to generate Android-style
Android.mk files from an autotools build system.
* This assumes that PA is run as the system daemon and configures
accordingly.
* In the Android build, libltdl is
12 matches
Mail list logo
