public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "James, Laura" <laurajames@attlabs.att.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Problems with NAND support
Date: Tue, 07 Aug 2001 17:01:22 +0100	[thread overview]
Message-ID: <19639.997200082@redhat.com> (raw)
In-Reply-To: <BB682C76EACAD311A6BD006008F5F7DC0112D50E@mpexchcl.attlabs.att.com>


laurajames@attlabs.att.com said:
> We're going to be working on a new board with large amounts of NAND
> flash in the immediate future. It would seem to be a much better idea
> to go with jffs2 than jffs.  What will we need to do to get it
> working? 

> Any pointers you can give will be very much appreciated.

Mainly:

1. Deal with the 10-write-per-page restriction on NAND chips. Probably just 
by keeping track of the number of writes to a page and when dishing out the 
tenth chunk (which will be rare, most nodes will be greater than 1/10 of a 
page) mark the remainder of the page as obsolete.

2. Ideally, we should do ECC instead of just the CRC we have at the moment.
We need to invent two new node types with ECC to parallel the original inode
and dirent nodes.

3. Be better about detecting bad blocks and treating them appropriately. 

--
dwmw2

  reply	other threads:[~2001-08-07 15:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 15:13 Problems with NAND support James, Laura
2001-08-07 16:01 ` David Woodhouse [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-06 15:00 Juan Ramon Jimenez
2001-08-07 10:26 ` David Woodhouse

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=19639.997200082@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=laurajames@attlabs.att.com \
    --cc=linux-mtd@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