From: "s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
To: Fabio Estevam <festevam@gmail.com>
Cc: "artem.bityutskiy@linux.intel.com"
<artem.bityutskiy@linux.intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Alex Gershgorin <alexg@meprolight.com>,
"u.kleine-koenig@pengutronix.de" <u.kleine-koenig@pengutronix.de>
Subject: Re: mtd mxc_nand: mx35 kernel panic during request to read Device ID
Date: Tue, 12 Jun 2012 18:16:54 +0200 [thread overview]
Message-ID: <20120612161654.GR30400@pengutronix.de> (raw)
In-Reply-To: <CAOMZO5A1xPzQs_7qMBPYJAPBu1OYc0wTRtibn-Kfu4=P6STgGA@mail.gmail.com>
On Tue, Jun 12, 2012 at 09:11:05AM -0300, Fabio Estevam wrote:
> Hi Alex,
>
> On Tue, Jun 12, 2012 at 7:35 AM, Alex Gershgorin <alexg@meprolight.com> wrote:
> > Hi everybody,
> >
> > In kernel 3.4, I have not encountered this problem
>
> Please try this patch:
> https://lkml.org/lkml/2012/6/8/366
This patch is necessary for the mxc_nand to work with flash based bbt.
However, without this patch the kernel won't crash.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-06-12 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 10:35 mtd mxc_nand: mx35 kernel panic during request to read Device ID Alex Gershgorin
2012-06-12 11:50 ` Uwe Kleine-König
2012-06-12 12:13 ` Alex Gershgorin
2012-06-12 16:20 ` s.hauer
2012-06-13 7:19 ` Alex Gershgorin
2012-06-12 12:11 ` Fabio Estevam
2012-06-12 12:25 ` Alex Gershgorin
2012-06-12 14:09 ` Fabio Estevam
2012-06-12 14:50 ` Alex Gershgorin
2012-06-12 16:16 ` s.hauer [this message]
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=20120612161654.GR30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alexg@meprolight.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=festevam@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=u.kleine-koenig@pengutronix.de \
/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).