From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Gaëtan Carlier" <gcembed@gmail.com>
Cc: Russell King <linux@arm.linux.org.uk>,
J.Lambrecht@TELEVIC.com, linux-mtd@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/1] mxc_nand : allow swapping the Bad block Indicator for NFC v1.
Date: Wed, 29 Aug 2012 10:56:01 +0300 [thread overview]
Message-ID: <1346226961.2848.424.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1345825064-9147-1-git-send-email-gcembed@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 569 bytes --]
On Fri, 2012-08-24 at 18:17 +0200, Gaëtan Carlier wrote:
> Swap the BI-byte on position 0x7D0 with a data byte at 0x835. To fix a bug
> in Freescale imx NFC v1 SoC's for 2K page NAND flashes: imx27 and imx31.
> Warning: The same solution needs to be applied to the boot loader and the
> flash programmer.
>
> This is a modified version of patch sent by Jürgen Lambrecht :
> [PATCH] Add 'config IMX_NFC_V1_BISWAP' to swap the Bad block Indicator,
> and use for imx27pdk nand support.
Pushed to l2-mtd.git, thanks!
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-08-29 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 13:04 [PATCH v2] mxc_nand : allow swapping the Bad block Indicator for NFC v1 Gaëtan Carlier
2012-08-24 12:28 ` Artem Bityutskiy
2012-08-24 16:17 ` [PATCH 1/1] " Gaëtan Carlier
2012-08-28 10:33 ` Gaëtan Carlier
2012-08-29 7:56 ` Artem Bityutskiy [this message]
2012-09-06 8:56 ` Juergen Beisert
2012-09-10 14:31 ` Gaëtan Carlier
2012-09-11 7:17 ` Sascha Hauer
2012-09-11 8:03 ` Gaëtan Carlier
2012-09-11 8:47 ` Sascha Hauer
2012-09-23 13:00 ` Artem Bityutskiy
2014-03-26 13:53 ` Gaëtan Carlier
2014-03-28 9:11 ` Sascha Hauer
2014-03-28 9:52 ` Gaëtan Carlier
2012-09-06 13:03 ` Juergen Beisert
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=1346226961.2848.424.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=J.Lambrecht@TELEVIC.com \
--cc=dwmw2@infradead.org \
--cc=gcembed@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.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 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).