From: acrux <acrux_it@libero.it>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Efika (mpc5200b): sound doesn't build/work from linux-2.6.38.x
Date: Sat, 4 Feb 2012 03:02:07 +0100 [thread overview]
Message-ID: <20120204030207.0d5cec19.acrux_it@libero.it> (raw)
In-Reply-To: <CAOZdJXU+kiQgsM9F3JVG3o8LV4oejSA1D85bFX+ZsqB7f9j_Ew@mail.gmail.com>
On Thu, 2 Feb 2012 21:50:02 +0000
Tabi Timur-B04825 <B04825@freescale.com> wrote:
> On Thu, Feb 2, 2012 at 10:57 AM, acrux <acrux_it@libero.it> wrote:
>
>
> > well, i got the same error with also linux-2.6.37. Btw, this was already reported about a year ago:
> > http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-February/088415.html
>
> I think this was fixed already. You're using an obsolete kernel.
>
hi Timur,
as i said [1] it seems to be fixed only in 3.x instead the last working one is the obsolete 2.6.36.x .
Anyway, alog the sound/soc/fsl/mpc5200_dma.c now builds the sound is still broken.
best,
--nico
[1]
On Thu, 2 Feb 2012 03:48:03 +0100
acrux <acrux_it@libero.it> wrote:
__omissis_
>
> With linux-3.0.18, linux-3.1.10 and linux-3.2.2 it builds but doesn't work.
> That's from my dmesg:
>
> [...]
> asoc: error - multiple DAI f0002200.sound registered with no name
> mpc5200-psc-ac97 f0002200.sound: Failed to register DAI
> mpc5200-psc-ac97: probe of f0002200.sound failed with error -22
>
acrux <acrux@cruxppc.org>
next prev parent reply other threads:[~2012-02-04 2:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-02 2:48 Efika (mpc5200b): sound doesn't build/work from linux-2.6.38.x acrux
2012-02-02 16:57 ` acrux
2012-02-02 21:50 ` Tabi Timur-B04825
2012-02-04 2:02 ` acrux [this message]
2012-02-05 15:25 ` Tabi Timur-B04825
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=20120204030207.0d5cec19.acrux_it@libero.it \
--to=acrux_it@libero.it \
--cc=B04825@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).