From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Cc: alsa-user@lists.sourceforge.net
Subject: Re: [ANN] ALSA 1.0.0pre1 is released
Date: Thu, 20 Nov 2003 17:47:23 +0100 [thread overview]
Message-ID: <s5hekw3yokk.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hn0as1hvn.wl@alsa2.suse.de>
At Wed, 19 Nov 2003 16:46:04 +0100,
I wrote:
>
> Hi all,
>
> as you might have already seen on the web news page, we released
> 1.0.0pre1 tarball. This is intended for the wide tests before the
> official 1.0.0 release. We planned to release 1.0.0 (hopefully) in
> this month, so please everyone test this version and give bug reports
> now.
>
> Especially, if you have a card or a mobo with ICH (or compatible)
> chip and *multiple* AC97 codecs, testing this version is appreciated.
> Please give (also positive) feedback whether it works. The handling
> of multiple codecs was changed recently, but not tested well because
> of lack of hardware.
>
>
> Important changes / fixes since 0.9.8
A couple of more important thing I forgot to mention about ALSA
library update:
- the default PCM API is in the new style.
If your app still uses the PCM API in the old style (i.e. without
defining ALSA_PCM_OLD_HW_PARAM_API), the compilation with the new
library may fail. In such a case, fix the API call with the new
style, or simply add
#define ALSA_PCM_OLD_HW_PARAMS_API
#define ALSA_PCM_OLD_SW_PARAMS_API
before inclusion of <alsa/asoundlib.h>. See alsa-lib/NOTES for
details.
The binary compatibility is kept with the new alsa-lib, so the
programs will run as well even after installing the new alsa-lib.
- SND_LIB_MAJOR is jumped to 1, and SND_LIB_MINOR is 0.
If your application checks the ALSA version with only SND_LIB_MINOR
macro, you'll need to fix it.
--
Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-11-20 16:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 15:46 [ANN] ALSA 1.0.0pre1 is released Takashi Iwai
2003-11-19 22:39 ` Paul Hanly (Hotmail)
2003-11-20 9:49 ` Takashi Iwai
2003-11-20 1:30 ` Fernando Pablo Lopez-Lezcano
2003-11-20 7:44 ` ALSA 1.0.0pre1 is released - intel8x0 is oopsing (2.6) R CHAN
2003-11-20 15:33 ` Takashi Iwai
2003-11-21 2:50 ` Re: ALSA 1.0.0pre1 is released - intel8x0 is oopsing (2.6) - FIXED! R CHAN
2003-11-20 9:53 ` [ANN] ALSA 1.0.0pre1 is released Takashi Iwai
2003-11-20 10:01 ` 1.0.0pre1 / ice1712 / mplayer-oss-delay Steffen Sauder
2003-11-20 11:08 ` Takashi Iwai
2003-11-20 16:47 ` Takashi Iwai [this message]
2003-11-20 18:30 ` [ANN] ALSA 1.0.0pre1 is released Dave Neuer
2003-11-20 18:45 ` [Alsa-user] " Takashi Iwai
2003-11-26 17:31 ` Kai Vehmanen
2003-11-26 17:37 ` Takashi Iwai
2003-11-26 17:45 ` Kai Vehmanen
2003-11-27 16:16 ` problems with intel8x0 and 1.0.0pre3 (was: Re: [ANN] ALSA 1.0.0pre1 is released) Kai Vehmanen
2003-11-27 16:23 ` Takashi Iwai
2003-11-27 18:08 ` Takashi Iwai
2003-11-28 14:06 ` Kai Vehmanen
2003-12-01 17:44 ` problems with intel8x0 and 1.0.0pre3 Kai Vehmanen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s5hekw3yokk.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=alsa-user@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox