From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: barat@medien.uni-weimar.de
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: migrating from old to new alsa-api
Date: Sat, 24 Apr 2004 16:52:36 +0100 [thread overview]
Message-ID: <408A8D44.7030405@superbug.demon.co.uk> (raw)
In-Reply-To: <Pine.LNX.4.56.0404221556500.4307@spring>
barat@medien.uni-weimar.de wrote:
> Hi,
> i need some clarifying about how the defines ALSA_PCM_OLD_HW_PARAMS_API
> etc. behaves.
> for alsa-1.x its clear that if the app uses the new api i have to define
> ALSA_PCM_NEW_HW_PARAMS_API, but what is for the case if i have an app with
> the new api and the user uses only alsa9? is alsa1.x then backwards
> compatible?
>
> regards
>
> Zsolt Barat
>
ALSA_PCM_NEW_HW_PARAMS_API etc. is for use with alsa0.9.x
That define is assumed to be the default for alsa1.x.x
ALSA_PCM_OLD_HW_PARAMS_API is for use with alsa1.x.x to make it behave
like "alsa0.9.x without the ALSA_PCM_NEW_HW_PARAMS_API".
Summary: -
To make your code work with bother alsa 0.9.x and 1.x.x, use
ALSA_PCM_NEW_HW_PARAMS_API etc. and then write your code to the 1.x.x api.
-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297
prev parent reply other threads:[~2004-04-24 15:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 13:57 migrating from old to new alsa-api barat
2004-04-22 14:11 ` Takashi Iwai
2004-04-24 15:52 ` James Courtier-Dutton [this message]
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=408A8D44.7030405@superbug.demon.co.uk \
--to=james@superbug.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=barat@medien.uni-weimar.de \
/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