On 10/13/2011 06:34 PM, Maarten Bosmans wrote:
2011/10/13 David Henningssondavid.hennings...@canonical.com:
Signed-off-by: David Henningssondavid.hennings...@canonical.com
---
src/modules/alsa/alsa-sink.c |8 ++--
src/modules/alsa/alsa-source.c |8 ++--
2 files changed, 12
2011/10/14 David Henningsson david.hennings...@canonical.com:
On 10/14/2011 11:42 AM, Feng Wei wrote:
2011/10/14 David Henningssondavid.hennings...@canonical.com:
On 10/14/2011 09:39 AM, Feng Wei wrote:
2011/10/14 David Henningssondavid.hennings...@canonical.com:
On 10/14/2011 04:47 AM,
On 10/14/2011 12:40 PM, Feng Wei wrote:
2011/10/14 David Henningssondavid.hennings...@canonical.com:
On 10/14/2011 11:42 AM, Feng Wei wrote:
2011/10/14 David Henningssondavid.hennings...@canonical.com:
On 10/14/2011 09:39 AM, Feng Wei wrote:
2011/10/14 David
On Fri, Oct 14, 2011 at 12:00:54PM +0200, David Henningsson wrote:
On 10/14/2011 11:39 AM, Mark Brown wrote:
On Fri, Oct 14, 2011 at 10:57:08AM +0200, David Henningsson wrote:
As for ports, this again depends on what is mutually exclusive and
what could be used in parallel, I vaguely remember
Hi,
I am one of the authors of the MeeGo policy system and currently
trying to do something similar @Intel. The original MeeGo policy
system was used in Nokia products (in N900 and in the currently
shipping N9).
In MeeGo we had a policy decision daemon that communicated its
routing, corking and
I am running PulseAudio on my laptop (Asus P50IJ) that has an Intel HDA
card (chipset VIA VT1708S, Linux 3.0.0, Debian wheezy).
The card basically has four mixer elements:
1. Master Front, which controls the master volume
2. Headphone, which does not seem to be doing anything
3. PCM -- obvious
On 10/14/2011 07:18 PM, Soeren D. Schulze wrote:
I am running PulseAudio on my laptop (Asus P50IJ) that has an Intel HDA
card (chipset VIA VT1708S, Linux 3.0.0, Debian wheezy).
VIA codecs are not that common. That's the main reason (I assume) its
chipset drivers are not as well standardised
From the discussions it seems that many other people tries to solve
the same problem. We, who made the MeeGo policy framework, concluded
that we need to either upstream our stuff or use/adopt the work that
is in progress.
This is excellent news!
The policy decision point would send profile
