All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Utikawa da Fonseca <marcelo.fonseca@tecnequip.com.br>
To: Mark Brown <broonie@sirena.org.uk>
Cc: alsa-devel@alsa-project.org
Subject: Re: Problem compiling soc - imx31 and wm8753
Date: Wed, 11 Mar 2009 14:08:44 -0300	[thread overview]
Message-ID: <49B7F01C.2070202@tecnequip.com.br> (raw)
In-Reply-To: <20090311153554.GB15629@sirena.org.uk>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii; format=flowed, Size: 2199 bytes --]

The i.MX31 Freescale's BSP does not have asoc support, just an interface 
for MC13783 (a Power Management IC from Freescale with integrated audio 
interface).
The wolfsonmicro's tree is the only one that have support to asoc but it 
does not compiles using the mentioned steps.
Am I missing something or may be these drivers broken?

Mark Brown escreveu:
> On Wed, Mar 11, 2009 at 11:47:25AM -0300, Marcelo Utikawa da Fonseca wrote:
>
>   
>> I am facing a problem while compiling the sound support for imx31ads board.
>> I got the kernel from wolfsonmicro using the following command:
>>     
>
>   
>> git clone git://opensource.wolfsonmicro.com/linux-2.6-asoc linux-2.6-asoc
>>     
>
>   
>> After this I just copy the arch/arm/configs/mx31ads_defconfig to .config 
>> and run:
>>     
>
>   
>> make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi- menuconfig
>>     
>
>   
>> I did not change nothing, just configure and compile...
>> My gcc version is 4.1.2 from Freescale.
>> What can be wrong? Could be this version of gcc a problem?
>> I already tried to correct the missing include files but the other 
>> errors are still there after the corrections...
>>     
>
> The i.MX31 support that is present in ASoC git depends on underlying
> support for the CPU which is not present in any mainline tree (which is
> why this code has not been contributed to mainline yet).
>
> Probably the easiest thing to do is to start from the BSP provided by
> Freescale - I believe that most versions of that contain the CPU audio
> drivers already, probably including a version of the WM8731 driver.  It
> should be much easier to merge that driver (by itself, just wm8731.c and
> wm8731.h) into the Freescale BSP than to merge the i.MX31 support into
> the standard kernel.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
>
>   


---------------------------------------------
Tecnequip Tecnologia em Equipamentos
Endereço/Address: Rua Juno, 527
Cidade/City: São Paulo
Estado/State: SP
País/Country: Brasil
CEP/Postal Code: 03445-000
Fone/Phone: 55-11-20937199
FAX: 55-11-29412289

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-03-11 17:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-11 14:47 Problem compiling soc - imx31 and wm8753 Marcelo Utikawa da Fonseca
2009-03-11 15:36 ` Mark Brown
2009-03-11 17:08   ` Marcelo Utikawa da Fonseca [this message]
2009-03-11 21:53     ` Mark Brown
2009-03-11 22:34       ` Liam Girdwood

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=49B7F01C.2070202@tecnequip.com.br \
    --to=marcelo.fonseca@tecnequip.com.br \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@sirena.org.uk \
    /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.