public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: linux-mtd@lists.infradead.org
Cc: Gagan Prakash <gagpcool@hkn.eecs.berkeley.edu>
Subject: Re: FAT on raw Nand
Date: Tue, 20 Sep 2005 13:32:31 +1200	[thread overview]
Message-ID: <200509201332.31431.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <Pine.LNX.4.44.0509191525180.1130-100000@hkn.eecs.berkeley.edu>

On Tuesday 20 September 2005 10:36, Gagan Prakash wrote:
> Hi
>
> I am trying to solve the problem of allowing a device with raw nand to be
> exposed to any Desktop OS (OS 10, Windows and Linux) without having to
> install any sort of driver on the Desktop OS that is not already present.
> The only solution I have read of/come up with is for the device to act as
> USB external drive and let the host OS mount it as a FAT filesystem. This
> means that the filesystem on device partition that is exposed needs to be
> FAT.

If you can't install any drivers then FAT is probably the only way to go for a 
FS.

The only alternative I can think of to this is to use ethernet + nfs  instead. 
ie. Your device looks like a USB ethernet device with a host running nfs  on 
the other end. That would allow you to run an alternative FS like YAFFS.

>
> Now from the archives I know its not the easiest and safest thing to
> expose a partition as FAT on raw nand. And it also requires the writing of
> a FTL layer. I was wondering if there is a better solution for this
> problem.
>
> For example is there a way to emulate FAT on top of existing nand fs like
> YAFFS or JFFS2 (this would seem hard specially for writes). Or is the only
> solution is to format the device as FAT and expose it as an external USB
> drive to the host OS.

Unfortunately there is no USB-NFS. There is only a USB mass storage device 
which can be used with most block file systems (typically FAT). USB-NFS would 
have been a good idea because it would allow devices to use their own FS 
internally.

The USB Mass Storage spec has no notion of a file system, just read/write 
blocks of data. To use YAFFS etc on the device and make it look like a USB 
mass storage device running FAT is probably too much to ask.

  reply	other threads:[~2005-09-20  1:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-19 22:36 FAT on raw Nand Gagan Prakash
2005-09-20  1:32 ` Charles Manning [this message]
2005-09-20  9:39   ` David Woodhouse
2005-09-21  3:45     ` FAT on raw Nand -->PTP Charles Manning
2005-09-20 10:26 ` FAT on raw Nand Simon Haynes

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=200509201332.31431.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=gagpcool@hkn.eecs.berkeley.edu \
    --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