public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@lumentis.se>
To: <mtd@infradead.org>
Subject: Nand Flash & JFFS
Date: Fri, 30 Mar 2001 15:01:55 +0200	[thread overview]
Message-ID: <000f01c0b919$99886e30$0a01a8c0@Win1> (raw)
In-Reply-To: <EADB10BAC266A14A85ECBF8686A73E310A9125@kolkrabbi.flaga.is>

[-- Attachment #1: Type: text/plain, Size: 994 bytes --]

Hi all

We are buliding a custom PPC860 board, which will use JFFS/JFFS2 as a root
file system which will hold all files we need. The FS must survive sudden
power loss.
My plan was to use NOR flash(128MB or more)which will partioned into a
Firmware/boot, 
raw linux kernel partition(if we can't find a boot SW will can boot linux
from JFFS) and the rest
will linux root FS with our apps.

Now, our HW guy wants to put NAND flash on since it is cheaper and has
higher density.
I dont think it's a good idea to have boot code in NAND flash due to the
possibility of
bad blocks, so I envision a board with a NOR flash as boot device and then
we could use NAND for a raw linux kernel partition and JFFS partition.

Is this a good idea?

Does JFFS/MTD support NAND flashes well yet?
Can it handle bad blocks?
Which chip models?
Which geometries are supported(4x8, 2x8 1x8)?
Can RedBoot(when JFFS support has been impl.) read a kernel from JFFS
and boot it?   

  Regards
           Joakim Tjernlund

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2064 bytes --]

      reply	other threads:[~2001-03-30 13:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-29 17:03 partitions and erase regions Kári Davíðsson
2001-03-30 13:01 ` Joakim Tjernlund [this message]

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='000f01c0b919$99886e30$0a01a8c0@Win1' \
    --to=joakim.tjernlund@lumentis.se \
    --cc=mtd@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