[alsa-devel] alsa-1.0.16
Hi,
Do you plan to release alsa-1.0.16?
Especially: - so that userland match kernel-2.6.24's subsystem - since alsa-lib has accumulated a number of bug fixes
Releasing would be helpful for distro than plan to release in the next few monthes...
Thanks.
On Wed, 16 Jan 2008, Thierry Vignaud wrote:
Hi,
Do you plan to release alsa-1.0.16?
Yes, it is my plan for next days.
Jaroslav
----- Jaroslav Kysela perex@perex.cz Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.
Takashi Iwai tiwai@suse.de writes:
Do you plan to release alsa-1.0.16?
Yes, it is my plan for next days.
Good to hear. Hopefully we'll have no many rc's...
Thanks :-)
What is the cutoff for getting a patch in for new hardware? I'm working on a project that I think we want support in 2.6.24, if alsa 1.0.16 is going in it.
On Wed, 2008-01-16 at 15:55 +0100, Thierry Vignaud wrote:
Takashi Iwai tiwai@suse.de writes:
Do you plan to release alsa-1.0.16?
Yes, it is my plan for next days.
Good to hear. Hopefully we'll have no many rc's...
Thanks :-) _______________________________________________ Alsa-devel mailing list Alsa-devel@alsa-project.org http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
Tobin Davis wrote:
What is the cutoff for getting a patch in for new hardware? I'm working on a project that I think we want support in 2.6.24, if alsa 1.0.16 is going in it.
2.6.24 is almost finished. It's too late for any major additions. The next target is 2.6.25, and the window for that will be open soon (once 2.6.24 is officially announced). You better hurry up!
I have the patch ready, just pending approval from my boss. It's for a new controller, and is only +3-4 lines (pci id & enumeration entries). Have to get it approved, as the product isn't due to launch until April (even though this patch is derived from a pre-production patch that Ubuntu has in their Gutsy desktop distribution).
Tobin
On Fri, 2008-01-18 at 09:39 +0100, Clemens Ladisch wrote:
Tobin Davis wrote:
What is the cutoff for getting a patch in for new hardware?
Support for new hardware shouldn't be a problem as long as it doesn't introduce risk of regressions for old hardware.
Regards, Clemens
participants (6)
-
Clemens Ladisch -
Jaroslav Kysela -
Takashi Iwai -
Thierry Vignaud -
Timur Tabi -
Tobin Davis