non functionable snd-ad1816a in Kernel 2.6.18-rc2
Hi everybody,
Just a reminder for everybody listening:
My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2.
I guess the reason for this is that Matthieu´s material is still residing in the mm-branch. Can I please have a constructive feedback where things are hanging after all that immense amount of time I spent to forward this issue? A thousands of thanks for Matthieu´s work one more time!
The bug ID is 6292, and the ACPI_PRODUCER reject patch is still missing in the main vanilla tree.
Regards
Uwe
Signature · 6 lines
Echte DSL-Flatrate dauerhaft für 0,- Euro*! "Feel free" mit GMX DSL! http://www.gmx.net/de/go/dsl - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 5 lines · Uwe Bugla
Just a reminder for everybody listening:
My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2.
I guess the reason for this is that Matthieu´s material is still residing in the mm-branch. Can I please have a constructive feedback where things are hanging after all that immense amount of time I spent to forward this issue? A thousands of thanks for Matthieu´s work one more time!
The bug ID is 6292, and theACPI_PRODUCERreject patch is still missing in the main vanilla tree.
Yup, the patch is in the -mm tree, and should make its way to the mainline vanilla kernel eventually. It does take a while, because we want to make sure it doesn't break somebody else's system while fixing yours.
Bjorn
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
-------- Original-Nachricht --------
Datum: Mon, 24 Jul 2006 13:40:56 -0600
Von: Bjorn Helgaas <[email protected]>
An: "Uwe Bugla" <[email protected]>
Betreff: Re: non functionable snd-ad1816a in Kernel 2.6.18-rc2
Quoted 9 lines · Uwe Bugla
Quoted 3 lines
Just a reminder for everybody listening:
My soundcard (snd-ad1816a) does not work in Kernel 2.6.18-rc2. I guess the reason for this is that Matthieu´s material is stillresiding in the mm-branch. Can I please have a constructive feedback where things are hanging after all that immense amount of time I spent to forward this issue?
Quoted 2 lines
A thousands of thanks for Matthieu´s work one more time!
The bug ID is 6292, and theACPI_PRODUCERreject patch is still missing
Quoted 10 lines
in the main vanilla tree.
Yup, the patch is in the -mm tree, and should make its way to the mainline vanilla kernel eventually. It does take a while, because we want to make sure it doesn't break somebody else's system while fixing yours.
Bjorn
OK so far.
But how can we make sure that it does not break somebody else´s system while fixing mine when anything deriving from the two Intel guys is NAK? If they would be a bit more cooperative things would go forward much faster I think.
I see this patchwork getting rusty in the mm-tree, and that can´t be it, can it?
Regards
Uwe
Signature · 6 lines
Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 3 lines · Uwe Bugla
But how can we make sure that it does not break somebody else´s system while fixing mine when anything deriving from the two Intel guys is NAK?
I don't understand. The idea is that people will test the -mm kernel and report any problems.
Quoted 2 lines
If they would be a bit more cooperative things would go forward much faster I think.
I think it's going about the right pace. Usually things stay in -mm for at least a month before we think about putting them upstream. And of course we don't push minor bugfixes upstream when we're close to an upstream release.
Bjorn
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html