From: Steve deRosier <derosier@pianodisc.com>
To: David Smoot <davidsmoot@gmail.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Setting up Alsa by hand on an embedded system
Date: Thu, 22 Dec 2005 09:46:17 -0800 [thread overview]
Message-ID: <43AAE669.9000703@pianodisc.com> (raw)
In-Reply-To: <b15982770512220753x72c28d9dxa60312f872bf1766@mail.gmail.com>
Hm, yeah, I missed the /usr/share/alsa stuff. Whoops.
We don't have python on our box, so I'd guess you'd be fine.
- Steve
David Smoot wrote:
> I don't the dir variable is the issue because I am not getting
> segfaults. The code compiles and works on my "host machine" (full
> debian box) but does not on my embedded.
>
> It appears that combining the two suggestions from Clements and Steve
> have gotten me further. It appears that the file /usr/share/alsa.conf
> loads the default configuration and also loads the file in
> /etc/asound.conf. I get a different error now, I think I need to tweak
> the files in /usr/share/alsa to match the correct chipset.
>
> Does the alsa configuration environment require python? My embedded
> system does not have python. I'm sure I will have to hack it in someday
> but it is not there yet.
>
> I've gotten further but a few more errors but I think you all have
> gotten me on the correct track. Thank you.
>
> David
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-22 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 1:36 Setting up Alsa by hand on an embedded system David Smoot
2005-12-22 9:05 ` Clemens Ladisch
2005-12-22 15:26 ` Asbjørn Sæbø
2005-12-22 15:53 ` David Smoot
2005-12-22 17:46 ` Steve deRosier [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-22 2:47 Steve DeRosier
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=43AAE669.9000703@pianodisc.com \
--to=derosier@pianodisc.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=davidsmoot@gmail.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.