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.
--
Backport alsa-1.0.11
https://launchpad.net/bugs/52543
--
ubuntu-backports mailing lis
** Changed in: dapper-backports (upstream)
Status: Unconfirmed => Confirmed
--
Backport alsa-1.0.11
https://launchpad.net/bugs/52543
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
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.
--
Backport alsa-1.0.11
https://launchpad.net/bugs/52543
--
ubuntu-backports mailing list
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
--
Backport alsa-1.0.11
htt
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 cer
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.
** Changed in: dapper-backports (upstream)
Status: Unconfirmed => Rejected
** Also affects: linux-s
(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?
** Changed in: dapper-backports (upstream)
Status: Confirmed => Unconfirmed
--
Backport alsa-1.0.11
https://launch
