From: Huang Shijie <b32955@freescale.com>
To: "Lothar Waßmann" <LW@KARO-electronics.de>
Cc: linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@freescale.com>
Subject: Re: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Tue, 19 Jul 2011 15:03:45 +0800 [thread overview]
Message-ID: <4E252C51.8070900@freescale.com> (raw)
In-Reply-To: <20005.7677.145955.789329@ipc1.ka-ro>
于 2011年07月19日 14:02, Lothar Waßmann 写道:
> Hi,
>
> Huang Shijie writes:
>> 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.
>>
> I have applied a patch (from the Freescale BSPs) that prevents JFFS2
> from using the OOB area. But this still doesn't help.
>
Could you show the log ?
>> 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.
>>
> What sort of DMA bug?
>
The DMA may time-out. :(
The DMA time-out may occur in two situations:
[1] send a command DMA descriptor, see the nfc->send_command() function.
[2] read the non-ecc data from nand, see the nfc->read_data() function.
I don't know why. Maybe caused by the timing, or something else.
Best Regards
Huang Shijie
> Lothar Waßmann
WARNING: multiple messages have this Message-ID (diff)
From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [i.MX28 GPMI] problem overwriting all-0xff data in NAND
Date: Tue, 19 Jul 2011 15:03:45 +0800 [thread overview]
Message-ID: <4E252C51.8070900@freescale.com> (raw)
In-Reply-To: <20005.7677.145955.789329@ipc1.ka-ro>
? 2011?07?19? 14:02, Lothar Wa?mann ??:
> Hi,
>
> Huang Shijie writes:
>> 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.
>>
> I have applied a patch (from the Freescale BSPs) that prevents JFFS2
> from using the OOB area. But this still doesn't help.
>
Could you show the log ?
>> 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.
>>
> What sort of DMA bug?
>
The DMA may time-out. :(
The DMA time-out may occur in two situations:
[1] send a command DMA descriptor, see the nfc->send_command() function.
[2] read the non-ecc data from nand, see the nfc->read_data() function.
I don't know why. Maybe caused by the timing, or something else.
Best Regards
Huang Shijie
> Lothar Wa?mann
next prev parent reply other threads:[~2011-07-19 7:03 UTC|newest]
Thread overview: 43+ 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 13:13 ` Lothar Waßmann
2011-07-18 14:56 ` Ivan Djelic
2011-07-18 14:56 ` Ivan Djelic
2011-07-19 5:59 ` Lothar Waßmann
2011-07-19 5:59 ` Lothar Waßmann
2011-07-19 6:48 ` Ivan Djelic
2011-07-19 6:48 ` Ivan Djelic
2011-07-18 16:43 ` Shawn Guo
2011-07-18 16:43 ` Shawn Guo
2011-07-19 2:12 ` Huang Shijie
2011-07-19 2:12 ` Huang Shijie
2011-07-19 6:02 ` Lothar Waßmann
2011-07-19 6:02 ` Lothar Waßmann
2011-07-19 7:03 ` Huang Shijie [this message]
2011-07-19 7:03 ` Huang Shijie
2011-07-19 9:55 ` Lothar Waßmann
2011-07-19 9:55 ` Lothar Waßmann
2011-07-19 13:36 ` Wolfram Sang
2011-07-19 13:36 ` Wolfram Sang
2011-07-20 2:18 ` Huang Shijie
2011-07-20 2:18 ` Huang Shijie
2011-07-20 8:51 ` Wolfram Sang
2011-07-20 8:51 ` Wolfram Sang
2011-07-20 10:34 ` Huang Shijie
2011-07-20 4:55 ` Huang Shijie
2011-07-20 4:55 ` Huang Shijie
2011-07-20 6:22 ` Lothar Waßmann
2011-07-20 6:22 ` Lothar Waßmann
2011-07-20 5:16 ` Artem Bityutskiy
2011-07-20 5:16 ` Artem Bityutskiy
2011-07-20 5:19 ` Artem Bityutskiy
2011-07-20 5:19 ` Artem Bityutskiy
2011-07-19 6:00 ` Lothar Waßmann
2011-07-19 6:00 ` Lothar Waßmann
2011-07-20 6:44 ` Huang Shijie
2011-07-20 6:44 ` Huang Shijie
2011-07-20 8:10 ` Lothar Waßmann
2011-07-20 8:10 ` Lothar Waßmann
2011-07-20 8:35 ` Artem Bityutskiy
2011-07-20 8:35 ` Artem Bityutskiy
2011-07-20 5:12 ` 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=4E252C51.8070900@freescale.com \
--to=b32955@freescale.com \
--cc=LW@KARO-electronics.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shawn.guo@freescale.com \
/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.