From: Lee Revell <rlrevell@joe-job.com>
To: Jaroslav Kysela <perex@suse.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: alsa-lib compatibility
Date: Wed, 18 Jan 2006 02:34:05 -0500 [thread overview]
Message-ID: <1137569646.30140.1.camel@mindpipe> (raw)
In-Reply-To: <Pine.LNX.4.61.0601041006310.9321@tm8103.perex-int.cz>
On Wed, 2006-01-04 at 10:12 +0100, Jaroslav Kysela wrote:
> Hi,
>
> it seems that it is quite required (based on current LKML
> discussion) to keep the alsa-lib compatibility with old drivers. Please,
> keep in mind that for example renaming of control names will break using
> old 2.6 kernel with new alsa-lib.
> The alsa-lib C code already checks for older drivers, but
> the extended configuration (like 5.1, s/pdif devices) in most cases
> changes a lot. We should add some runtime checks which driver version
> is running in XXXXX.conf files and apply the old behaviour if required.
>
> Any comments?
> Jaroslav
>
How do you propose we solve this problem:
/usr/lib/mozilla-firefox/firefox-bin: relocation
error: /usr/lib/libalsatoss.so.0: symbol
snd_pcm_hw_params_set_rate_near, version ALSA_0.9.0rc4 not defined in
file libasound.so.2 with link time reference
My apps are compiled against alsa-lib 1.0.9 but I have 1.0.11-rc2
installed.
Lee
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next prev parent reply other threads:[~2006-01-18 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 9:12 alsa-lib compatibility Jaroslav Kysela
2006-01-04 12:10 ` Takashi Iwai
2006-01-18 7:34 ` Lee Revell [this message]
2006-01-18 8:48 ` Jaroslav Kysela
2006-01-18 9:08 ` Lee Revell
2006-01-18 9:13 ` Jaroslav Kysela
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=1137569646.30140.1.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@alsa-project.org \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.