From: "Joseph M Dupre (AVAB Inc.)" <dupre@avab.com>
To: linux-mtd@lists.infradead.org
Subject: Do I need TrueFFS on INFTL Disk-On-Chip?
Date: Fri, 21 Oct 2005 16:44:42 -0700 [thread overview]
Message-ID: <43591AFA.21753.1B79E87@localhost> (raw)
I am a bit confused over the functions of nftl/inftl and TrueFFS in
regards to wear-leveling on DOC devices.
The DOC 2000 devices come pre-partitioned with a FAT filesystem on a
"disk" (BDTL) partition. It is my understanding that what M-Systems
calls "TrueFFS" is loaded at boot time from the "binary" (BDK)
partition. Is it this TrueFFS that sits between the FAT filesystem
and the flash that does all the necessary wear-leveling?
I am assuming that if I reformat the disk (BDTL) partition to Ext2 or
Ext3 or whatever using linux fdisk and mkfs, the TrueFFS is still
sitting there doing the job of wear leveling on whatever filesystem I
choose to use on the DOC. Is this correct?
So what happens when I re-write the BDK partition with code like
DOCboot or Grub? Is the wear leveling mechanism gone at that point
or is wear-leveling part of the "inftl" layer which still exists?
Where does the "inftl" reside? Is that part of the DOC or the
kernel?
Please advise before I burn out my DOC!
- Joe
next reply other threads:[~2005-10-21 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-21 23:44 Joseph M Dupre (AVAB Inc.) [this message]
2005-10-24 13:31 ` Do I need TrueFFS on INFTL Disk-On-Chip? Dan Brown
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=43591AFA.21753.1B79E87@localhost \
--to=dupre@avab.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