From: Thomas Gleixner <tglx@linutronix.de>
To: Han Chang <posaune@hotmail.com>
Cc: manningc2@actrix.gen.nz, linux-mtd@lists.infradead.org
Subject: Re: FAT vs jFFS2 for NAND.
Date: Thu, 15 Jun 2006 09:53:13 +0200 [thread overview]
Message-ID: <1150357994.5257.481.camel@localhost.localdomain> (raw)
In-Reply-To: <BAY110-F252049B6BCEE0BB50A7CC3BC820@phx.gbl>
On Wed, 2006-06-14 at 17:34 -0700, Han Chang wrote:
> Thanks for the information. Now I started to make FAT work on NAND.
> "mkdosfs" uses ioctl to check if the device is a floppy disk or hard disk,
> but NAND is neither of these, so it fails. Is there any way to get around
> this?
The only way which would make sense to a certain degree is to resurrect
the SmartMedia Format driver, which bitrots in the old MTD CVS. It is
designed to allow FAT on NAND FLASH, but I have no idea whats the
current status of that code is.
> Should I do fdisk on the NAND device, if I can already create partition in
> the driver initiation?
A parition does not transform NAND into a block device. You need to use
the block device driver of MTD. Be warned that you will wear out your
FLASH in foreseable time and data loss on powerfail is guaranteed by
design.
Is there any real good reason why you want to use FAT on a FLASH?
tglx
next prev parent reply other threads:[~2006-06-15 14:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 2:58 FAT vs jFFS2 for NAND Han Chang
2006-05-28 5:54 ` Charles Manning
2006-06-15 0:34 ` Han Chang
2006-06-15 7:53 ` Thomas Gleixner [this message]
2006-06-19 18:31 ` Han Chang
2006-06-19 18:38 ` Thomas Gleixner
2006-06-19 20:23 ` David Woodhouse
2006-06-19 21:10 ` Charles Manning
2006-06-20 11:31 ` Claudio Lanconelli
2006-06-20 12:30 ` David Woodhouse
2006-06-20 13:25 ` Claudio Lanconelli
2006-06-20 13:52 ` Thomas Gleixner
2006-06-20 17:26 ` Claudio Lanconelli
2006-06-20 17:41 ` Thomas Gleixner
2006-06-21 14:15 ` Claudio Lanconelli
2006-06-21 18:19 ` 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=1150357994.5257.481.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=manningc2@actrix.gen.nz \
--cc=posaune@hotmail.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