From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Szabolcs Erki <szabolcs@szabolcserki.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Developing and cross-compiling an ASoC driver
Date: Thu, 22 Oct 2009 15:52:58 +0100 [thread overview]
Message-ID: <20091022145258.GA14571@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <786228398.20091022164034@szabolcserki.com>
On Thu, Oct 22, 2009 at 04:40:34PM +0200, Szabolcs Erki wrote:
Please don't top post, it breaks the flow of discussion and removes
context from your reply.
> Ok, so ASoC is totally platform-independent, there is no patch to be
> applied against ASoC in order to make it feasible for the target. Is
ASoC itself is platform independant. It does require drivers for the
CPU, CODEC and board that it is to be used with. You mentioned that you
are using an Atmel processor which does have CPU side support in current
Linux versions though the ADC you mentioned doesn't.
> it correct? In this case I have to compile it in the kernel, using the
> gcc-arm-elf cross compiler. How to do that? Hard copy the files and
> hacking makefiles together?
> Because the descriptions I found applied to installing ASoC on a desktop environment, like
> Ubuntu.
ASoC is part of the standard Linux kernel, just build the kernel as you
would normally. As I said in my previous mail people working with the
same embedded Linux distribution as you are would be the best people to
ask about this, it is not at all ASoC or ALSA specific.
next prev parent reply other threads:[~2009-10-22 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 14:08 Developing and cross-compiling an ASoC driver Szabolcs Erki
2009-10-22 14:21 ` Mark Brown
2009-10-22 14:40 ` Szabolcs Erki
2009-10-22 14:52 ` Mark Brown [this message]
2009-10-22 15:05 ` Szabolcs Erki
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=20091022145258.GA14571@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=szabolcs@szabolcserki.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.