From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Josh Boyer <jdub@us.ibm.com>
Cc: haverkam@de.ibm.com, linux-mtd@lists.infradead.org
Subject: Re: NAND partitioning
Date: Mon, 31 Jan 2005 13:56:13 +0100 [thread overview]
Message-ID: <20050131125613.GA6345@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1107013860.10670.5.camel@windu.rchland.ibm.com>
On Sat, 29 January 2005 09:51:00 -0600, Josh Boyer wrote:
>
> Not necessarily. I was actually thinking of having JFFS2 just "ignore"
> such eraseblocks. Essentially treating them as bad blocks perhaps.
>
> However, such blocks could be scattered across the entire device rather
> than contained within a certain address range on the chip. Updating the
> data would be a bit tricky, which is why I said a driver would need to
> be created in order to deal with it.
Problem would be trivial to solve, if said blocks were not scattered
across the device. Do you have a good reason to need this?
Jörn
--
I don't understand it. Nobody does.
-- Richard P. Feynman
next prev parent reply other threads:[~2005-01-31 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 21:03 NAND partitioning Josh Boyer
2005-01-29 11:39 ` Artem B. Bityuckiy
2005-01-29 15:51 ` Josh Boyer
2005-01-30 15:51 ` Artem B. Bityuckiy
2005-01-31 12:56 ` Jörn Engel [this message]
2005-01-31 15:10 ` Josh Boyer
2005-01-31 15:29 ` Jörn Engel
2005-01-31 16:54 ` Josh Boyer
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=20050131125613.GA6345@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=haverkam@de.ibm.com \
--cc=jdub@us.ibm.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