From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Enric Balletbo i Serra <eballetbo@gmail.com>,
"kyungmin.park" <kyungmin.park@samsung.com>
Cc: m.szyprowski@samsung.com, dwmw2@infradead.org,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
adrian.hunter@nokia.com
Subject: Re: [PATCH 1/1] mtd: OneNAND: fix bufferram management when chip has 2-planes.
Date: Tue, 26 Oct 2010 12:36:01 +0300 [thread overview]
Message-ID: <1288085761.2227.40.camel@localhost> (raw)
In-Reply-To: <1287841434-3349-2-git-send-email-eballetbo@gmail.com>
On Sat, 2010-10-23 at 15:43 +0200, Enric Balletbo i Serra wrote:
> This patch adds code that I think was lost when it was applied the commit
> 5988af2319781bc8e0ce418affec4e09cfa77907 - mtd: Flex-OneNAND support
>
> Test case:
> 1. Stress a jffs2 filesystem using
> bonnie++ -u 0:0 -s 32 -m 16 -r 16
> 2. dmesg shows various 'Header CRC failed' errors like:
> Header CRC failed on REF_PRISTINE node at 0x1e81315c: Read 0x000000e0,
> calculated 0x564fc9e8
>
> Tested on IGEP v2 board with a Muxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)
> with 2 planes from Numonyx and CONFIG_MTD_ONENAND_2X_PROGRAM set to y
>
> Signed-off-by: Enric Balletbo i Serra <eballetbo@gmail.com>
Kyungmin, would be nice to have your ack/nack.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Enric Balletbo i Serra <eballetbo@gmail.com>,
"kyungmin.park" <kyungmin.park@samsung.com>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
dwmw2@infradead.org, adrian.hunter@nokia.com,
m.szyprowski@samsung.com
Subject: Re: [PATCH 1/1] mtd: OneNAND: fix bufferram management when chip has 2-planes.
Date: Tue, 26 Oct 2010 12:36:01 +0300 [thread overview]
Message-ID: <1288085761.2227.40.camel@localhost> (raw)
In-Reply-To: <1287841434-3349-2-git-send-email-eballetbo@gmail.com>
On Sat, 2010-10-23 at 15:43 +0200, Enric Balletbo i Serra wrote:
> This patch adds code that I think was lost when it was applied the commit
> 5988af2319781bc8e0ce418affec4e09cfa77907 - mtd: Flex-OneNAND support
>
> Test case:
> 1. Stress a jffs2 filesystem using
> bonnie++ -u 0:0 -s 32 -m 16 -r 16
> 2. dmesg shows various 'Header CRC failed' errors like:
> Header CRC failed on REF_PRISTINE node at 0x1e81315c: Read 0x000000e0,
> calculated 0x564fc9e8
>
> Tested on IGEP v2 board with a Muxed OneNAND(DDP) 512MB 1.8V 16-bit (0x58)
> with 2 planes from Numonyx and CONFIG_MTD_ONENAND_2X_PROGRAM set to y
>
> Signed-off-by: Enric Balletbo i Serra <eballetbo@gmail.com>
Kyungmin, would be nice to have your ack/nack.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-10-26 9:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-23 13:43 [PATCH 0/1] mtd: OneNAND: fix bufferram management Enric Balletbo i Serra
2010-10-23 13:43 ` [PATCH 1/1] mtd: OneNAND: fix bufferram management when chip has 2-planes Enric Balletbo i Serra
2010-10-26 9:36 ` Artem Bityutskiy [this message]
2010-10-26 9:36 ` Artem Bityutskiy
2010-10-26 10:29 ` Kyungmin Park
2010-10-26 10:29 ` Kyungmin Park
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=1288085761.2227.40.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=dwmw2@infradead.org \
--cc=eballetbo@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=m.szyprowski@samsung.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.