From: Sascha Hauer <s.hauer@pengutronix.de>
To: "Gaëtan Carlier" <gcembed@gmail.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
J.Lambrecht@televic.com, Juergen Beisert <jbe@pengutronix.de>,
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: Fri, 28 Mar 2014 10:11:42 +0100 [thread overview]
Message-ID: <20140328091142.GE17250@pengutronix.de> (raw)
In-Reply-To: <5332DBDD.4090802@gmail.com>
On Wed, Mar 26, 2014 at 02:53:33PM +0100, Gaëtan Carlier wrote:
> Hi,
> I don't see where the problem is. The fact that bad block marker are
> used or not, is not related to "my" patch. This patch just places
> data where they should be. If I take the Nand and connect it to a
> not-bugged NFC controller, all data will be read correctly with data
> is main area and OOB is spare area.
> >
> >In this form the patch is simply not correct and should be dropped.
> >
> Now I want to adapt and publish my platform file to latest kernel
> version and I am still stopped with this biswap patch that is not
> applied. As I said before, I must not be the only that have used
> this damned original patch from Freescale that swaps byte in their
> ATK programming soft, redboot and Kernel and it is impossible to
> fallback to current NAND handling (without swapping).
>
> Is there any chance that if I send this patch against
> linux-next/master branch, it will be finally accepted. Only people
> that needs it will use it. There is so much option in menuconfig
> with so little explaination and mark as "Only say Yes if you known
> what you do".
I'm ok with supporting a devicetree option that decides whether to do
bad block marker swapping or not. It shouldn't be a Kconfig option.
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 |
next prev parent reply other threads:[~2014-03-28 9:12 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
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 [this message]
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=20140328091142.GE17250@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=J.Lambrecht@televic.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gcembed@gmail.com \
--cc=jbe@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.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).