All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Vipin Malik <vmalik@danielind.com>
Cc: jffs-dev <jffs-dev@axis.com>, mtd <mtd@infradead.org>
Subject: Re: First cut at MTD/JFFS HOWTO
Date: Tue, 13 Feb 2001 09:15:47 +0000	[thread overview]
Message-ID: <10792.982055747@redhat.com> (raw)
In-Reply-To: <3A886BED.9339AC4F@danielind.com>


vmalik@danielind.com said:
> Q. Why another file system. What was wrong with ext2? 
> A. 

Standard response - need journalling pseudo-filesystem to emulate a block 
device and to wear levelling. then need ext3 (note 3) on that. journalling 
fs on top of journalling fs - not efficient. Also, no way for ext[23] to 
mark blocks as _deleted_ and no longer cared about. Fill ext2 partition on 
NFTL, empty it again, and the NFTL will still carefully copy around the 
blocks containing old deleted data.

> Q. Do I have to have JFFS on MTD? 
> A. 

ATM yes. Once you could do it on a block device. People are talking about 
making me make it work on IDE devices (CF). But I don't want to :)

> Q. What is DOC (disk on chip)? A. 

Bunch of NAND flash chips connected together with a clever ASIC which does 
hardware ECC.

> Q. What File systems can I have on DOC? A. 

If you put NFTL on it to emulate a block device (the status quo) then any 
normal filesystem. JFFS ought to work too.

> Q. What is Flash memory? A. 
> Q. What is CFI Flash memory? A. 
> Q. What is JDEC Flash memory? A.
> Q. What is this "interleave" stuff? A.

If you have 16-bit chips, but a 32-bit processor, it makes sense to arrange 
them side-by-side to fill the CPU's bus. You drive them both 
simultaneously. That's the arrangement we refer to as 'interleave'. 

Other possibilities are... 4x 8-bit chips on 32-bit bus, 2x8-bit 
chips on 16-bit bus, ...


#include <compact_flash_is_not_flash.h>


--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

  parent reply	other threads:[~2001-02-13  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-12 23:04 First cut at MTD/JFFS HOWTO Vipin Malik
2001-02-13  8:21 ` Johan Adolfsson
2001-02-13  9:08 ` David Woodhouse
2001-02-13  9:09 ` David Woodhouse
2001-02-13  9:15 ` David Woodhouse [this message]
2001-02-13  9:33   ` MTD device minor numbers, documentation wrong? Johan Adolfsson
2001-02-13 10:05     ` David Woodhouse
2001-02-13 17:45   ` Second cut at MTD/JFFS HOWTO Vipin Malik

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=10792.982055747@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=mtd@infradead.org \
    --cc=vmalik@danielind.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.