Dear Mr. Warren,
I recently upgraded my laptop to Debian testing (from Debian stable +
the longterm stable 3.0.x kernel). The newer kernel 3.2.x came with a
regression that git bisect has traced down to one of your commits in
the early 3.1.x kernel development stage (git bisect output and git
bise
At Wed, 22 Feb 2012 01:43:44 -0500,
Andres Cimmarusti wrote:
>
> [1 ]
> Dear Mr. Warren,
>
> I recently upgraded my laptop to Debian testing (from Debian stable +
> the longterm stable 3.0.x kernel). The newer kernel 3.2.x came with a
> regression that git bisect has traced down to one of your c
Andres Cimmarusti wrote at Tuesday, February 21, 2012 11:44 PM:
...
> Unfortunately with kernel 3.2.x and 3.1.x I get no sound out choosing the same
> configuration in pulseaudio. Device is advertised correctly but
> there's a bizarre multiplicity advertised:
>
> $ aplay -l
> List of PLAYBACK
Stephen Warren wrote:
> As Takashi mentions, from a kernel perspective, this isn't really a
> regression at all, but simply exposing all the features of the HW that
> were previously hidden. Without that change, others can't use some HW
> usefully at all. Unfortunately, pulseaudio makes some rathe
First of all, thank you for your feedback. It's been quite helpful / insightful
> The biggest problem is that PA checks only the first HDMI device.
> In that sense, this is no regression in the kernel side, although I
> know it's annoying.
I agree this seems more like a shortcoming of pulseaudio.
Andres Cimmarusti wrote at Wednesday, February 22, 2012 5:02 PM:
> First of all, thank you for your feedback. It's been quite helpful /
> insightful
...
> > There are ways to configure pulseaudio to allow the user to select which
> > PCM device to use on a given sound card. David Henningsson made
On 02/23/2012 01:01 AM, Andres Cimmarusti wrote:
If the new two pins can be never used, i.e. physically unreachable,
we may disable these pins by giving the proper default pin-config
values. Usually it's a job of BIOS. But if BIOS doesn't do it, user
need to do it manually.
Build your kernel w
David Henningsson wrote at Thursday, February 23, 2012 1:31 AM:
> On 02/23/2012 01:01 AM, Andres Cimmarusti wrote:
> >> If the new two pins can be never used, i.e. physically unreachable,
> >> we may disable these pins by giving the proper default pin-config
> >> values. Usually it's a job of BIOS
8 matches
Mail list logo
