From: Mark Brown <broonie@sirena.org.uk>
To: Arun KS <arunks@mistralsolutions.com>
Cc: alsa-devel@alsa-project.org,
"linux-omap@vger.kernel.org List" <linux-omap@vger.kernel.org>,
Jesslyn Abdul Salam <jesslyn.abdulsalam@gmail.com>
Subject: Re: AIC23 SOC Driver on OSK5912
Date: Tue, 7 Oct 2008 16:12:15 +0100 [thread overview]
Message-ID: <20081007151214.GH19835@sirena.org.uk> (raw)
In-Reply-To: <dfeb90390810070809r481f1a55wba410516bf2d1e9e@mail.gmail.com>
On Tue, Oct 07, 2008 at 08:39:07PM +0530, Arun KS wrote:
> On Tue, Oct 7, 2008 at 7:20 PM, Jesslyn Abdul Salam
> > Not yet. Would please share what you have done to make it work ? Also when I
> > tried to strace aplay , it keeps looking for a
> > </share/alsa/cards/tlv320aic23.conf> file which is not there in the alsa-lib
> > package. Any idea what goes in that file ?
> CCing in l-o mailing list too.
> I dont know about that file. I didnt face that issue.
It's perfectly normal to check that file, it doesn't need to be there -
it contains optional ALSA control configuration for the card in the same
format as the other files in there. Note that usually it'd appear in
/usr/share rather than /usr, this may indicate that your ALSA user space
is not configured as one would expect.
next prev parent reply other threads:[~2008-10-07 15:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 11:48 AIC23 SOC Driver on OSK5912 Jesslyn Abdul Salam
2008-10-07 11:54 ` Mark Brown
2008-10-07 12:02 ` Arun KS
[not found] ` <e762f7a90810070506q2d4e299eqe2d6d9bc515aeec0@mail.gmail.com>
2008-10-07 12:06 ` Fwd: " Jesslyn Abdul Salam
2008-10-07 12:18 ` Jesslyn Abdul Salam
[not found] ` <48EB6820.3090809@mistralsolutions.com>
2008-10-07 13:50 ` Jesslyn Abdul Salam
2008-10-07 15:09 ` [alsa-devel] " Arun KS
2008-10-07 15:12 ` Mark Brown [this message]
2008-10-08 10:42 ` Jesslyn Abdul Salam
2008-10-07 12:19 ` Fwd: " Arun KS
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=20081007151214.GH19835@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=arunks@mistralsolutions.com \
--cc=jesslyn.abdulsalam@gmail.com \
--cc=linux-omap@vger.kernel.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 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.