* alsa-lib compatibility
@ 2006-01-04 9:12 Jaroslav Kysela
2006-01-04 12:10 ` Takashi Iwai
2006-01-18 7:34 ` Lee Revell
0 siblings, 2 replies; 6+ messages in thread
From: Jaroslav Kysela @ 2006-01-04 9:12 UTC (permalink / raw)
To: ALSA development
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
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: alsa-lib compatibility
2006-01-04 9:12 alsa-lib compatibility Jaroslav Kysela
@ 2006-01-04 12:10 ` Takashi Iwai
2006-01-18 7:34 ` Lee Revell
1 sibling, 0 replies; 6+ messages in thread
From: Takashi Iwai @ 2006-01-04 12:10 UTC (permalink / raw)
To: Jaroslav Kysela; +Cc: ALSA development
At Wed, 4 Jan 2006 10:12:13 +0100 (CET),
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.
Agreed. I proposed a similiar proposal sometime ago but got no
comments at that time ;)
Takashi
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: alsa-lib compatibility
2006-01-04 9:12 alsa-lib compatibility Jaroslav Kysela
2006-01-04 12:10 ` Takashi Iwai
@ 2006-01-18 7:34 ` Lee Revell
2006-01-18 8:48 ` Jaroslav Kysela
1 sibling, 1 reply; 6+ messages in thread
From: Lee Revell @ 2006-01-18 7:34 UTC (permalink / raw)
To: Jaroslav Kysela; +Cc: ALSA development
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: alsa-lib compatibility
2006-01-18 7:34 ` Lee Revell
@ 2006-01-18 8:48 ` Jaroslav Kysela
2006-01-18 9:08 ` Lee Revell
0 siblings, 1 reply; 6+ messages in thread
From: Jaroslav Kysela @ 2006-01-18 8:48 UTC (permalink / raw)
To: Lee Revell; +Cc: ALSA development
On Wed, 18 Jan 2006, Lee Revell wrote:
> 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
Hmm. It should work. The libasound.so.2 should have this symbol defined:
perex@tm8103:~/alsa/alsa-lib/src/.libs> nm libasound.so.2 | grep rate_near | grep rc4
00041460 T snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
and the libalsatoss.0.0.0:
perex@tm8103:~/alsa/alsa-oss/alsa> nm .libs/libalsatoss.0.0.0 | grep rate_near
U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
Could you check it?
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: alsa-lib compatibility
2006-01-18 8:48 ` Jaroslav Kysela
@ 2006-01-18 9:08 ` Lee Revell
2006-01-18 9:13 ` Jaroslav Kysela
0 siblings, 1 reply; 6+ messages in thread
From: Lee Revell @ 2006-01-18 9:08 UTC (permalink / raw)
To: Jaroslav Kysela; +Cc: ALSA development
On Wed, 2006-01-18 at 09:48 +0100, Jaroslav Kysela wrote:
> On Wed, 18 Jan 2006, Lee Revell wrote:
>
> > 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
>
> Hmm. It should work. The libasound.so.2 should have this symbol defined:
>
> perex@tm8103:~/alsa/alsa-lib/src/.libs> nm libasound.so.2 | grep rate_near | grep rc4
> 00041460 T snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
>
> and the libalsatoss.0.0.0:
>
> perex@tm8103:~/alsa/alsa-oss/alsa> nm .libs/libalsatoss.0.0.0 | grep rate_near
> U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
>
> Could you check it?
>
I got different output. But, I think the problem was I forgot to
install the newer alsa-oss.
$ nm /usr/lib/libasound.so.2.0.0 | grep rate_near
00044f63 t __old_snd_pcm_hw_params_set_rate_near
00040ff5 T __snd_pcm_hw_params_set_rate_near
00040ff5 W snd_pcm_hw_params_set_rate_near
$ nm /usr/lib/libalsatoss.so.0.0.0 | grep rate_near
U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: alsa-lib compatibility
2006-01-18 9:08 ` Lee Revell
@ 2006-01-18 9:13 ` Jaroslav Kysela
0 siblings, 0 replies; 6+ messages in thread
From: Jaroslav Kysela @ 2006-01-18 9:13 UTC (permalink / raw)
To: Lee Revell; +Cc: ALSA development
On Wed, 18 Jan 2006, Lee Revell wrote:
> On Wed, 2006-01-18 at 09:48 +0100, Jaroslav Kysela wrote:
> > On Wed, 18 Jan 2006, Lee Revell wrote:
> >
> > > 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
> >
> > Hmm. It should work. The libasound.so.2 should have this symbol defined:
> >
> > perex@tm8103:~/alsa/alsa-lib/src/.libs> nm libasound.so.2 | grep rate_near | grep rc4
> > 00041460 T snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
> >
> > and the libalsatoss.0.0.0:
> >
> > perex@tm8103:~/alsa/alsa-oss/alsa> nm .libs/libalsatoss.0.0.0 | grep rate_near
> > U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
> >
> > Could you check it?
> >
>
> I got different output. But, I think the problem was I forgot to
> install the newer alsa-oss.
>
> $ nm /usr/lib/libasound.so.2.0.0 | grep rate_near
> 00044f63 t __old_snd_pcm_hw_params_set_rate_near
> 00040ff5 T __snd_pcm_hw_params_set_rate_near
> 00040ff5 W snd_pcm_hw_params_set_rate_near
>
> $ nm /usr/lib/libalsatoss.so.0.0.0 | grep rate_near
> U snd_pcm_hw_params_set_rate_near@@ALSA_0.9.0rc4
The libalsatoss library is fine, but alsa-lib was probably compiled
without versioned symbols (it's the default so I wonder why). Could you
retest with your distro?
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SUSE Labs
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-01-18 9:13 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-04 9:12 alsa-lib compatibility Jaroslav Kysela
2006-01-04 12:10 ` Takashi Iwai
2006-01-18 7:34 ` Lee Revell
2006-01-18 8:48 ` Jaroslav Kysela
2006-01-18 9:08 ` Lee Revell
2006-01-18 9:13 ` Jaroslav Kysela
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.