Backport alsa-1.0.11

(re-marking as unconfirmed)

How does Alsa backporting work? I was always under the impression that doing so requires appropriate changes/alsa patches in the kernel, correct?

in effect it is not so easy.
The core driver are in the kernel and you have to patch direclty the kernel.
This is not so easy because I think dapper kernel is only open for security bugs and critical ones.

Then, unfortunately, I will not be able to do it.

The kernel is still open for "bugfixes", so I'll subscribe this bug over to the kernel team and see what they think.

I'm sorry about this.

Rejecting on the basis that most of the patches in current alsa are actually in dapper kernel.

If there's some specific problem, please search the bug reports to see if it is already reported, or open a new bug report. A complete backport of the entire alsa tree will not happen for dapper, and certainly will not be done just to satisfy one problem by one user.

Ben, so is the Dapper kernel capable of supporting this newer version of Alsa, or are you saying the bugfixes in the newer alsa are already pretty much in Dapper's kernel?

I can still see a lot of alsa work being done in the Dapper git tree. Thanks for your great work

Never mind; I understand what you're saying now, after re-reading your post.

Thanks for your input, Ben.

Leaving the Backport request as rejected; file specific ALSA bugs in their appropriate locations.