From: Thomas Gleixner <gleixner@autronix.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: jffs-dev@axis.com, linux-mtd@lists.infradead.org
Subject: Re: NAND flash and JFFS(2)
Date: Mon, 11 Feb 2002 20:28:09 +0100 [thread overview]
Message-ID: <0202112028090B.00764@thomas> (raw)
In-Reply-To: <02021116483807.00764@thomas>
On Monday, 11. February 2002 16:48, Thomas Gleixner wrote:
> I reflected this question again and we should do this very careful before
> implemetation. If we choose the same layout, somebody would be able to
> implement the SmartMedia DOS fs on top of SmartMedia and raw NAND flash.
> I personally have not interest in this fs, it's ok for MP3 players and
> digicams but not for industrial use.
I had a look at the nand driver, where we have to do some changes anyway to
support a different ECC address. To get the flexibility to use either a JFFS2
specific ECC scheme or a different scheme like the SmartMedia DOS-FAT i will
add a array to the nand structure, which holds the positions of the ECC bytes
inside the spare area and a flag, which can be used to support the virtual
pagesize of 512 Byte for small NAND devices (if anybody is going to implement
this).
The filesystem driver can set the ECC byte positions, so they match it's
requirements. We could add config options to select a default ECC scheme, so
we have access to the chip as char device too. I'm not sure if we need this
really.
So we have the flexibility to do what we want and we don't prevent anybody
from implementing a different system.
I will try it with the following scheme tonight:
SmartMedia and raw NAND 512 byte pagesize
Byte 0-3 ECC part 1
Byte 4 page data valid flag
Byte 5 bad block status
Byte 6-7 ECC part 2
Byte 8-15 cleanmarker
SmartMedia and raw NAND 256 Byte pagesize
Byte 0-2 ECC
Byte 3 spare
Byte 4 page data valid flag
Byte 5 bad block status
Byte 6-7 cleanmarker
I have both card types so i can verify that it works.
Thomas
__________________________________________________
Thomas Gleixner, autronix automation GmbH
auf dem berg 3, d-88690 uhldingen-muehlhofen
fon: +49 7556 919891 , fax: +49 7556 919886
mail: gleixner@autronix.de, http://www.autronix.de
next prev parent reply other threads:[~2002-02-11 19:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 15:32 NAND flash and JFFS(2) Thomas Gleixner
2002-02-11 15:48 ` Thomas Gleixner
2002-02-11 19:28 ` Thomas Gleixner [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-13 20:03 Lance Nakamura
2002-02-13 20:19 ` Thomas Gleixner
2002-02-11 23:42 Steve_Chen
2002-02-12 0:10 ` Thomas Gleixner
[not found] <02020523405103.11497@thomas>
2002-02-06 4:54 ` David Woodhouse
2002-02-06 22:47 ` Thomas Gleixner
2002-02-06 22:55 ` David Woodhouse
2002-02-07 6:51 ` Thomas Gleixner
2002-02-07 7:04 ` David Woodhouse
2002-02-11 13:42 ` Thomas Gleixner
2002-02-11 13:53 ` David Woodhouse
[not found] ` <0202121847440K.00764@thomas>
2002-02-13 11:40 ` Thomas Gleixner
2002-02-05 14:41 Veli-Pekka Ylönen
2002-02-05 15:30 ` David Woodhouse
2002-02-05 17:28 ` Thomas Gleixner
2002-02-05 21:18 ` David Woodhouse
2002-02-05 17:35 ` Veli-Pekka Ylönen
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=0202112028090B.00764@thomas \
--to=gleixner@autronix.de \
--cc=dwmw2@infradead.org \
--cc=jffs-dev@axis.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