public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Dan Brown" <brown@osdsun1.nrl.navy.mil>
To: "Slim" <slimaffi@yahoo.com>, <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] Towards DiskOnChip support as a NAND driver
Date: Wed, 16 Jun 2004 16:23:24 -0400	[thread overview]
Message-ID: <083701c453df$c65db960$0100a8c0@superfortress> (raw)
In-Reply-To: 20040616161345.33330.qmail@web50802.mail.yahoo.com

A few answers:

> Is the doc2000 dip NFTL or INFTL?  With read only support, would I be
> able to create a filesystem to read?

Some are NFTL, some are INFTL.  The INFTL variant is sometimes also known as
DiskOnChip 2000 TSOP.  From the pdf file that comes with the DOS-based DOC
utilities (hint hint):

[Inverse NAND Flash Translation Layer] M-Systems' latest flash management
algorithm, used by the TrueFFS driver for the following devices:
- DiskOnChip Millennium Plus

- Mobile DiskOnChip Plus

- DiskOnChip 2000 DIP (high), 384Mbytes and higher.

- DiskOnChip 2000 DIP (low), 192Mbytes and higher.

As for read-only support, its only the bad-block table itself that's
read-only, not the device itself.  Sorry, I should have been clearer in my
message.  If more blocks go bad at runtime, the information won't be
recorded to flash, and you'll forget about these additional bad blocks at
poweroff (which is bad).  Unless you're using INFTL filesystem, which has
its own markers for post-sale bad blocks.  Except INFTL doesn't work with
this driver yet. :(

The ability to update the BBT is something I plan to add soon, since I need
it. :)

You should be able to create a filesystem, but as I mentioned I haven't
gotten JFFS2 to work for me, yet.

> ECC - hardware error correction by the device?  Is this an optional
> enable in the driver?

Yes, the DOC has an ASIC that does ECC computation (for actual error
correction, software assitance is required).  It's not optional, though it
could be made so....  Why would you want to turn it off?

> Does it support other filesystems (ext2/3)?

Once the (I)NFTL code works with this driver, you can put filesystems like
ext2/3 over (I)NFTL.  For reasons why you might not want to, read up on
JFFS2.

> Thanks to everyone working on this.  I've needed a driver for doc2000
> dip devices for a couple years now.

Yeah, me too, but until now I kept hoping David would do it in his copious
spare time :)

    -Dan

  reply	other threads:[~2004-06-16 20:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BacpZ-0008CJ-KT@canuck.infradead.org>
2004-06-16 16:13 ` [PATCH] Towards DiskOnChip support as a NAND driver Slim
2004-06-16 20:23   ` Dan Brown [this message]
2004-06-16 21:47     ` Thomas Gleixner
2004-06-16 14:19 Dan Brown
2004-06-16 22:32 ` Thomas Gleixner
2004-06-16 22:46   ` David Woodhouse
2004-06-16 22:50     ` Thomas Gleixner

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='083701c453df$c65db960$0100a8c0@superfortress' \
    --to=brown@osdsun1.nrl.navy.mil \
    --cc=linux-mtd@lists.infradead.org \
    --cc=slimaffi@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox