public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Sudeep K N" <sudeep.holla@gmail.com>
To: dwmw2@infradead.org, rpurdie@openedhand.com
Cc: linux-mtd@lists.infradead.org
Subject: Spare area access information from JFFS2
Date: Sat, 5 May 2007 21:48:18 +0530	[thread overview]
Message-ID: <a1e50e4b0705050918j73dfc01cnd9fdb667f19b31f1@mail.gmail.com> (raw)

Hi,

       We are working on Nand Flash Controller which does not support
       ECC protection during Spare_Only Operation, rather it supports
       ECC protection for both Main_and_Spare area. In this regard,
       before to implement any workaround in my nand driver we want to
       know "Spare Area and Spare + Main area access sequence" from
       JFFS2 filesystem perspective during any JFFS2 operation.

       Proceeding further to observe JFFS2 Spare area access we found the
       the following:

       1. During Mount: scans the block, [erases], and writes "0x20031985"
               into the spare area on start of every block followed by another
               18 bytes which spans across multiple pages because free bytes in
               spare area is only 4
       2. Later during main page program operation our nand controller
               updates spare area ECC bytes, during this sequence we are not
               clear whether JFFS2 perform any spare operation to updates it
               meta data.
       3. Also, we want know, later the above sequence, does JFFS2 performs
               any spare only program operations.


Regards,
Sudeep

             reply	other threads:[~2007-05-05 16:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-05 16:18 Sudeep K N [this message]
2007-05-06  6:01 ` Spare area access information from JFFS2 Thomas Gleixner

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=a1e50e4b0705050918j73dfc01cnd9fdb667f19b31f1@mail.gmail.com \
    --to=sudeep.holla@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rpurdie@openedhand.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox