The patch was merged to ALSA CVS so you may check the new alsa-driver
(when it comes) or download the affected file from ALSA CVS and merge it
to the latest driver package.
how-to is here - http://people.redhat.com/stransky/alsa
Ma.
Sadda Teh wrote:
Understood, I'm assuming that the changes will go into the kernel once
they release their next RC (I hope). In the meantime I'll try to compile
in the patch myself and see if it actually makes a difference. BTW,
great kernel compilation instructions in the release notes. Thanks to
whoever wrote those. Now, I'll go pester the folks at Alsa to get that
patch upstream.
On 3/21/06, *Dan Williams* <dcbw@xxxxxxxxxx <mailto:dcbw@xxxxxxxxxx>> wrote:
On Tue, 2006-03-21 at 13:57 -0500, Sadda Teh wrote:
> Might anyone be willing to apply the patch mentioned here:
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1895> (You have
> to click the Guest Login link to view)
>
> I, and probably many others have a motherboard affected by this bug.
> It would be much appreciated if the fix would make it into FC5.
> Thanks!
Unless patches are crashers, they likely won't make it into FC5 without
being in the upstream kernel. Work with the ALSA project to make sure
that patch gets into the upstream kernel ASAP, and it will show up in
Fedora quite soon after that.
Part of this is for quality reasons; if the patch makes it into the
kernel, then it's likely it's good enough. It's also for API reasons
and maintainability. The less different Fedora kernels are from
upstream "vanilla" kernels, the less work it is to update Fedora kernels
every time a new upstream kernel is released.
Dan
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx <mailto:fedora-devel-list@xxxxxxxxxx>
https://www.redhat.com/mailman/listinfo/fedora-devel-list
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
