From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Brent Weatherall <brentweatherall@gmail.com>
Cc: Peter Ujfalusi <peter.ujfalusi@ti.com>,
alsa-devel@alsa-project.org, Clemens Ladisch <clemens@ladisch.de>
Subject: Re: PandaBoard ES Audio Problems
Date: Thu, 31 Jan 2013 19:50:41 +0000 [thread overview]
Message-ID: <1359661841.10392.17.camel@loki> (raw)
In-Reply-To: <CAAo96ZDNUY8Sp=kmjGXy5Ro0q7x22XVtO3Uv0VhhJBugUvOfTw@mail.gmail.com>
> Thank you for taking the time to look this over. Is there an aplay
> command that might uncover if there is a valid path to the device, or
> does the ability to play sound with aplay demonstrate the presence of
> the path?
>
Working aplay/arecord will show the path is valid.
Liam
>
>
>
>
>
next prev parent reply other threads:[~2013-01-31 19:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 16:51 PandaBoard ES Audio Problems Brent Weatherall
2013-01-31 17:28 ` Clemens Ladisch
2013-01-31 18:23 ` Liam Girdwood
2013-01-31 19:24 ` Brent Weatherall
2013-01-31 19:44 ` Clemens Ladisch
2013-01-31 19:50 ` Brent Weatherall
2013-01-31 20:00 ` Liam Girdwood
2013-01-31 22:13 ` Brent Weatherall
2013-02-01 8:29 ` Liam Girdwood
2013-02-01 10:51 ` Peter Ujfalusi
2013-02-01 10:56 ` Michael Trimarchi
2013-01-31 19:50 ` Liam Girdwood [this message]
2013-02-01 6:57 ` Takashi Iwai
2013-02-01 12:53 ` Peter Ujfalusi
2013-02-06 15:10 ` [PATCH 0/2] ASoC: OMAP4+ABE (ubuntu): Might fix OpenMax on PandaBoard Peter Ujfalusi
2013-02-06 15:10 ` [PATCH 1/2] ASoC: omap-abe-mmap: Make the hwrule function to be more generic Peter Ujfalusi
2013-02-06 15:10 ` [PATCH 2/2] ASoC: omap-abe-mmap: Place constraint to buffer size as well Peter Ujfalusi
2013-02-06 15:37 ` [PATCH 0/2] ASoC: OMAP4+ABE (ubuntu): Might fix OpenMax on PandaBoard Brent Weatherall
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=1359661841.10392.17.camel@loki \
--to=liam.r.girdwood@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=brentweatherall@gmail.com \
--cc=clemens@ladisch.de \
--cc=peter.ujfalusi@ti.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.