public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: dedekind1@gmail.com (Artem Bityutskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Wed, 20 Jul 2011 08:16:35 +0300	[thread overview]
Message-ID: <1311139000.20738.146.camel@sauron> (raw)
In-Reply-To: <4E24E804.10002@freescale.com>

On Tue, 2011-07-19 at 10:12 +0800, Huang Shijie wrote:
> hi  Lothar:
> > On Mon, Jul 18, 2011 at 03:13:27PM +0200, Lothar Wa?mann wrote:
> >> Hi,
> >>
> >> with the gpmi-nfc driver for imx28 from Shawn Guo on a TX28 I
> > To be clear, the author of gpmi-nfc driver is Huang Shijie (Cc-ed).
> >
> > Regards,
> > Shawn
> >
> >> encountered some problems with jffs2 when overwriting pages that have
> >> been written with 0xff (e.g. from padding from the file system image
> >> file).
> The GPMI driver now does not support the JFFS2 very well.
> The JFFS2 will write the OOB, while the BCH of GPMI will use the OOB too.
> So I have to disable the JFFS2 to use the OOB. I have not finish the 
> code about it now.
> 
> I recommend you use the UBIFS. But the latest version of GPMI driver 
> meets a DMA bug.
> I am debugging the DMA bug now. and I will send it out when i fix it.

This is a different issue. You refer to the "GPMI-controlled flash has
no space in OOB for JFFS2". Lothar's issue is about "GPMI-controlled
flash does not allow writing 0xFFs and then writing something else",
which is very normal.

-- 
Best Regards,
Artem Bityutskiy

  parent reply	other threads:[~2011-07-20  5:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-18 13:13 [i.MX28 GPMI] problem overwriting all-0xff data in NAND Lothar Waßmann
2011-07-18 14:56 ` Ivan Djelic
2011-07-19  5:59   ` Lothar Waßmann
2011-07-19  6:48     ` Ivan Djelic
2011-07-18 16:43 ` Shawn Guo
2011-07-19  2:12   ` Huang Shijie
2011-07-19  6:02     ` Lothar Waßmann
2011-07-19  7:03       ` Huang Shijie
2011-07-19  9:55         ` Lothar Waßmann
2011-07-19 13:36           ` Wolfram Sang
2011-07-20  2:18             ` Huang Shijie
2011-07-20  8:51               ` Wolfram Sang
2011-07-20  4:55           ` Huang Shijie
2011-07-20  6:22             ` Lothar Waßmann
2011-07-20  5:16     ` Artem Bityutskiy [this message]
2011-07-20  5:19       ` Artem Bityutskiy
2011-07-19  6:00   ` Lothar Waßmann
2011-07-20  6:44   ` Huang Shijie
2011-07-20  8:10     ` Lothar Waßmann
2011-07-20  8:35     ` Artem Bityutskiy
2011-07-20  5:12 ` Artem Bityutskiy

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=1311139000.20738.146.camel@sauron \
    --to=dedekind1@gmail.com \
    --cc=linux-arm-kernel@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