[Maverick] (pre-stable) ALSA: HDA: Enable internal speaker on Dell M101z

[David Henningsson]

On 2010-09-16 19:28, Leann Ogasawara wrote:
> On Thu, 2010-09-16 at 10:00 +0200, David Henningsson wrote:
>> BugLink: http://launchpad.net/bugs/640254
>>
>> In some cases a magic processing coefficient is needed to enable
>> the internal speaker on Dell M101z. According to Realtek, this
>> processing coefficient is only present on ALC269vb.
>>
>> Btw, this time I have checked - it applies cleanly to the
>> ubuntu-maverick git tree. :-)
>>
>> Signed-off-by: David Henningsson<david.henningsson at canonical.com>
>
> Looks good to me.  Also looks to be in Takashi's tree and Cc'd to
> stable:
>
> http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commit;h=145a902bfeb1f89a41165bd2d1e633ce070bcb73
>
> As we're now currently in Kernel Freeze for Maverick we now have to
> abide by the Kernel SRU policy [1].

Oh, just when you thought you had learned the rules, the rules change...:-(
In addition, I thought I would get away as long as it was Thursday 
anywhere in the world. Looks like I was wrong.

> Care to add the SRU Justification
> to the bug?

I'm unsure whether it can be SRU justified. "Simple, obvious and short 
fixes or hardware enablement patches as long as the next release has not 
reached beta status." It is a simple hardware enablement patch, but what 
does "the next release" refer to here, Maverick or Natty?

> We also need 2 additional Ack's before applying.  Here's
> mine.
>
> Acked-by: Leann Ogasawara<leann.ogasawara at canonical.com>
>
> This might have the possibility of making it for Maverick's final
> release should the kernel require uploading for a release critical bug
> fix.  Otherwise, it'll have to wait for one of the first post-release
> SRU's.

Anyway, as it has been applied upstream and cc:ed to stable, perhaps we 
should just let it wait for either the first SRU, or the upstream 
stable, whatever happens first.

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic