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 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. Thanks again. Szabolcs Thursday, October 22, 2009, 4:21:48 PM, you wrote: > 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. > _______________________________________________ > Alsa-devel mailing list > Alsa-devel@xxxxxxxxxxxxxxxx > http://mailman.alsa-project.org/mailman/listinfo/alsa-devel -- Szabolcs Erki szabolcs@xxxxxxxxxxxxxxxx Read my blog at http://www.szabolcserki.com/ _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
