From: Hou-xiang ZHU <hou-xiang.zhu@st.com>
To: alsa-devel@alsa-project.org
Subject: alsa_aplay doesn't work on android on hdk7108
Date: Thu, 29 Sep 2011 19:17:02 +0800 [thread overview]
Message-ID: <4E8453AE.7040201@st.com> (raw)
Hello,
I am trying to add alsa feature to Android on hdk7108 (which is sh4
architecture, not arm).
Basically on non android linux platform ,i.e STLinux-2.4, the driver and
alsa-libs and alsa-utils works with the following test command:
---------------------------
#aplay -v -t raw -D hw:1,0 -c 2 -r 32000 -f S16_BE /32K_16Bit_Stereo.pcm"
---------------------------
But when working on Android platform, because the alsa-lib/alsa-utils
are different from STLinux-2.4, so we ask someone the two packages from
a arm platform. and compilation ok.
but during run alsa_aplay, the following error occurred:
-----------------------------------
#/system/bin/alsa_aplay -v -t raw -D hw:1,0 -c 2 -r 32000 -f S16_BE
/32K_16Bit_Stereo.pcm
ALSA lib
vendor/STMicroelectronics/hdk7108/alsa/alsa-lib/src/confmisc.c:137:(snd_config_get_bool)
confmisc.c in func snd_config_get_bool line 137 Invalid type for nonblock
ALSA lib
vendor/STMicroelectronics/hdk7108/alsa/alsa-lib/src/pcm/pcm_hw.c:1417:(_snd_pcm_hw_open)
Invalid type for subdevice
aplay: main:656: in aplay.c func main line 656 audio open error: Invalid
argument
aplay/main.c in func main line 452
alsa-lib/src/pcm/pcm.c func snd_pcm_open line 2242 after call
snd_config_update(), err=1
----------------------------------
looks like alsa configuration issue. I noticed that on STLinux-2.4
platform, the alsa-libs is 1.0.21a and on android platform, it is
1.0.16, can this be a issue?
or configuration file wrong or else? how to debug this?
Thanks you very much!
Houxiang
reply other threads:[~2011-09-29 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E8453AE.7040201@st.com \
--to=hou-xiang.zhu@st.com \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).