All of lore.kernel.org
 help / color / mirror / Atom feed
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:21:48 +0100	[thread overview]
Message-ID: <20091022142148.GE3776@sirena.org.uk> (raw)
In-Reply-To: <1608652916.20091022160818@szabolcserki.com>

On Thu, Oct 22, 2009 at 04:08:18PM +0200, Szabolcs Erki wrote:

> I didn't find any suitable description how to do a cross-platform driver development process.
> Could you please give me some introduction how to:

> - cross compile alsa-driver (AFAIK ASoC is part of it, and ALSA is
> part of the linux kernel), and alsa-utils (for getting arecord)
> - cross compile the newly developed alsa driver
> - integrate ASoC and the custom driver to the patched kernel
> (Linux4SAM) and cross compile them to one image.

There is nothing particularly special about building when you're
developing a new driver - the kernel is built in exactly the same way.
There's certainly nothing ASoC specific here.  You'll probably get more
useful advice by asking people who normally use the same distribution
that you do how they develop.

Many people build a system as they normally would with the distribution
they usually use (eg, OpenEmbedded) and then use the toolchain that has 
to compile a kernel by hand from a regular git checkout, copying the
resulting kernel into whatever images they normally use.

  reply	other threads:[~2009-10-22 14:21 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 [this message]
2009-10-22 14:40   ` Szabolcs Erki
2009-10-22 14:52     ` Mark Brown
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=20091022142148.GE3776@sirena.org.uk \
    --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.