From: Jonathan Andrews <jon@jonshouse.co.uk>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Request for help CM109 on arm board
Date: Tue, 07 Feb 2012 22:21:53 +0000 [thread overview]
Message-ID: <1328653313.889.15.camel@jonspc> (raw)
In-Reply-To: <4F319B47.2080703@ladisch.de>
On Tue, 2012-02-07 at 22:44 +0100, Clemens Ladisch wrote:
> Jonathan Andrews wrote:
> > ALSA lib timer.c:189:(snd_timer_open_noupdate) Unknown timer hw:CLASS=3,SCLASS=0,CARD=0,DEV=0,SUBDEV=0
>
> > ARM # cat /usr/share/alsa/alsa.conf
> > ...
>
> You have deleted alsa-lib's basic device definitions. Device-specific
> definitions are supposed to go into /usr/share/alsa/cards/. Your
> definitions look as if they are supposed to go into /etc/asound.conf.
>
Thanks for the reply. I've failed to create the basic device
definitions..
I have alsa-lib-1.0.25 cross compiled from source, the libs are
installed and alsa-utils-1.0.25 has been built against it.
The snag is alsaconf seems broken (fails to exec) and as I don't have an
ldd that works with arm i'm a bit bust, everything else in alsa-utils
seems to at least execute ....
Do I need to split the config across files, I only want one device on
this board and i'm limited in space. I have kernel+kernel modules
+busybox+some libs+alsautils partially working and i'm out of flash..
I figured as I need only one device on one board that will never change
I could hand code it, is it a requirement to split the config. This is
destined to be a single task machine.
Thanks,
Jon
prev parent reply other threads:[~2012-02-07 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-07 16:00 Request for help CM109 on arm board Jonathan Andrews
2012-02-07 20:35 ` Jonathan Andrews
2012-02-07 21:44 ` Clemens Ladisch
2012-02-07 22:21 ` Jonathan Andrews [this message]
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=1328653313.889.15.camel@jonspc \
--to=jon@jonshouse.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
/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.