From: Nicolin Chen <Guangyu.Chen@freescale.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Nicolin Chen <b42378@freescale.com>,
Mark Brown <broonie@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: mx6: Audio does not work on linux-next 20140107
Date: Wed, 8 Jan 2014 17:53:03 +0800 [thread overview]
Message-ID: <20140108095301.GA12854@MrMyself> (raw)
In-Reply-To: <CAOMZO5C0_aEzSB+fJuyfxCisojUewS9i33kA4-rVB2-NHaFOgw@mail.gmail.com>
On Wed, Jan 08, 2014 at 08:01:56AM -0200, Fabio Estevam wrote:
> Hi Nicolin,
>
> On Wed, Jan 8, 2014 at 3:04 AM, Nicolin Chen <Guangyu.Chen@freescale.com> wrote:
>
> > I think it is impossible to run SDMA without firmware, which stores all
> > the scripts we need, including Audio's one. Although the upstream kernel
> > doesn't have firmware, the reason why you were able to run audio playback
> > is because you have the firmware in your rootfs. So since the driver's
> > upgraded, it's plausible for us to upgrade the firmware as well. But I
>
> No, this is not correct.
>
Yea, Shawn just told me there's an inner firmware in the ROM code while
this firmware only supports some basic scripts. And I've already sent
my fixing patches (you're in the to list). Please take a look and test
if you can.
Thank you,
Nicolin Chen
next prev parent reply other threads:[~2014-01-08 10:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 11:56 mx6: Audio does not work on linux-next 20140107 Fabio Estevam
2014-01-07 12:07 ` Lars-Peter Clausen
2014-01-07 12:29 ` Fabio Estevam
2014-01-07 12:28 ` Nicolin Chen
2014-01-07 12:49 ` Fabio Estevam
2014-01-08 3:50 ` Fabio Estevam
2014-01-08 5:04 ` Nicolin Chen
2014-01-08 10:01 ` Fabio Estevam
2014-01-08 9:53 ` Nicolin Chen [this message]
2014-01-08 15:33 ` Fabio Estevam
2014-01-07 12:50 ` Lars-Peter Clausen
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=20140108095301.GA12854@MrMyself \
--to=guangyu.chen@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=b42378@freescale.com \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lars@metafoo.de \
--cc=shawn.guo@linaro.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 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.