From: stan <ghjeold_i_mwee@cox.net>
To: "Mitul Sen (misen)" <misen@cisco.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Setting format to SND_PCM_FORMAT_MU_LAW does not let me apply hardware parameters
Date: Tue, 01 Jul 2008 15:12:22 -0700 [thread overview]
Message-ID: <486AABC6.6020906@cox.net> (raw)
In-Reply-To: <3B6F5C9068D5864096EB291236C3386F03B35428@xmb-sjc-21d.amer.cisco.com>
Mitul Sen (misen) wrote:
>
> Thanks for your suggestions. For the first suggestion, how would I
> know the version of alsa-lib that I am using so that I can download
> the source code for the same? Is alsa-lib the same as libasound? Under
> /usr/lib/libasound.so I have a symbolic link to libasound.so.2.0.0. Is
> that then the version I should be looking for?
>
> I am really new to this so please excuse me if these questions are too
> basic for this forum!
>
> Thanks,
> Mitul
>
Good queston. I know because of the package. You can find the driver
version by running cat /proc/asound/version and the utilities
version by running aplay --version .
I couldn't find a way to get the library version. You can use the run
alsa-info.sh --no-upload and the output will have the driver,
library, and tool version at the top.
The script is found at http://www.alsa-project.org/alsa-info.sh
libasound is always version 2.0.0, no matter the alsa-lib version. I
presume that is to facilitate testing and upgrading. Nothing will break
with newer versions. So that is unrelated to alsa version.
You can find the latest beta versions of all the alsa source here
http://www.alsa-project.org/main/index.php/Changes_v1.0.17rc2_v1.0.17rc3
And a link to the latest stable release here
http://www.alsa-project.org
next prev parent reply other threads:[~2008-07-01 22:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 22:09 Setting format to SND_PCM_FORMAT_MU_LAW does not let me apply hardware parameters Mitul Sen (misen)
2008-07-01 7:39 ` Clemens Ladisch
2008-07-01 17:01 ` Mitul Sen (misen)
2008-07-01 13:59 ` stan
2008-07-01 18:42 ` Mitul Sen (misen)
2008-07-01 22:12 ` stan [this message]
2008-07-01 23:50 ` Mitul Sen (misen)
2008-07-02 2:20 ` stan
2008-07-03 18:55 ` Mitul Sen (misen)
2008-07-16 23:36 ` Mitul Sen (misen)
2008-07-17 3:30 ` stan
2008-07-23 0:11 ` Mitul Sen (misen)
2008-07-23 18:25 ` stan
2008-07-23 21:31 ` Mitul Sen (misen)
2008-07-24 0:46 ` stan
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=486AABC6.6020906@cox.net \
--to=ghjeold_i_mwee@cox.net \
--cc=alsa-devel@alsa-project.org \
--cc=misen@cisco.com \
/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.