From: Ezequiel Garcia <ezequiel.garcia@imgtec.com>
To: "\"Qi Wang 王起 (qiwang)\"" <qiwang@micron.com>,
"Brian Norris" <computersforpeace@gmail.com>,
"abrestic@chromium.org" <abrestic@chromium.org>,
"ionela.voinescu@imgtec.com" <ionela.voinescu@imgtec.com>,
"James Hartley" <james.hartley@imgtec.com>,
"arnaud.mouiche@invoxia.com" <arnaud.mouiche@invoxia.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Cc: "\"Frank Liu 刘群 (frankliu)\"" <frankliu@micron.com>,
"\"Peter Pan 潘栋 (peterpandong)\"" <peterpandong@micron.com>
Subject: Re: [PATCH 6/6] mtd: spi-nand: Support common SPI NAND devices
Date: Wed, 3 Dec 2014 17:18:06 -0300 [thread overview]
Message-ID: <547F6FFE.6070000@imgtec.com> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A77136F67@NTXXIAMBX02.xacn.micron.com>
On 12/03/2014 09:08 AM, Qi Wang 王起 (qiwang) wrote:
[..]
>>> For example, Jffs2 program clean marker data to oob first when format
>>> operation, then will program main data into NAND flash main area when
>> normal write operation.
>>> That mean JFFS2 can only store clean marker into unprotect area of oob.
>>
>> Yeah, but are these devices capable of writing to the OOB region only
>> (without messing with the data) ?
>
> Yes, SPI NAND have this capability. SPI NAND also have definition for NOP,
> just similar with Parallel NAND, fill 0xFF to the area that don't want to
> write anything is ok.
>
Which SPI NAND command allows to do this?
AFAICS, you need to issue the following sequence to be able to write to
only the main area, or only the OOB area:
1. Read page to cache
2. Write to cache
3. Write page from cache
So it doesn't seem to support it natively, but through a workaround.
Doesn't this hurt JFFS2 performance a lot?
[..]
>>
>> Do you have any reason for *not* using a UBI-based FS?
>
> I agree with you, I just considered some legacy users customer still using JFFS2.
>
Hm.. right. It's important to support legacy users, but I'd say it's not
our primary goal.
--
Ezequiel
next prev parent reply other threads:[~2014-12-03 20:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 9:52 [PATCH 6/6] mtd: spi-nand: Support common SPI NAND devices Qi Wang 王起 (qiwang)
2014-12-03 11:13 ` Ezequiel Garcia
2014-12-03 12:08 ` Qi Wang 王起 (qiwang)
2014-12-03 20:18 ` Ezequiel Garcia [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-02 12:58 [PATCH 0/6] SPI NAND for everyone Ezequiel Garcia
2014-12-02 12:58 ` [PATCH 6/6] mtd: spi-nand: Support common SPI NAND devices Ezequiel Garcia
2014-12-13 1:27 ` Daniel Ehrenberg
2014-12-15 19:36 ` Ezequiel Garcia
2014-12-15 20:17 ` Daniel Ehrenberg
[not found] ` <87F60714EC601C4C83DFF1D2E3D390A049EE65@NTXXIAMBX02.xacn.micron.com>
2014-12-22 4:34 ` Qi Wang 王起 (qiwang)
2014-12-22 16:16 ` Ezequiel Garcia
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=547F6FFE.6070000@imgtec.com \
--to=ezequiel.garcia@imgtec.com \
--cc=abrestic@chromium.org \
--cc=arnaud.mouiche@invoxia.com \
--cc=computersforpeace@gmail.com \
--cc=frankliu@micron.com \
--cc=ionela.voinescu@imgtec.com \
--cc=james.hartley@imgtec.com \
--cc=linux-mtd@lists.infradead.org \
--cc=peterpandong@micron.com \
--cc=qiwang@micron.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.