public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Charles Manning <manningc2@actrix.gen.nz>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Han Chang <posaune@hotmail.com>,
	tglx@linutronix.de, linux-mtd@lists.infradead.org
Subject: Re: FAT vs jFFS2 for NAND.
Date: Tue, 20 Jun 2006 09:10:41 +1200	[thread overview]
Message-ID: <200606200910.41974.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <1150748626.2646.7.camel@shinybook.infradead.org>

On Tuesday 20 June 2006 08:23, David Woodhouse wrote:
> On Mon, 2006-06-19 at 11:31 -0700, Han Chang wrote:
> > Thanks! The reason for using FAT on the NAND is when the device has the
> > NAND is connected to a PC via USB, it can appear to be storage device
> > read by the PC user directly.
>
> Can't you use the 'PTP' USB protocol, which is designed for sharing
> pictures? It can also share an arbitrary file system, I believe.

I looked at PTP a while back. This is very picture centric and is no use for 
general file transfer.

There's also a newer (and as-yet unratified) protocol that allows transfers of 
other files. These allow transfer of other file types, but still don't 
support a full fs.

A USB-ftp would be a GoodThing.

>
> Failing that, SmartMedia makes a certain amount of sense. Use the code
> from the CVS tree as a basis, or just do it yourself (using the
> mtd_blkdevs helper stuff which we already use for nftl etc.)

Unfortiunately USB Mass Storage (with a Windows host) pretty much forces the 
use of FAT on top of a block driver.  The SmartMedia block driver model is 
suffieciently robust (FAT corruptions are far more likely to cause failures).

-- CHarles

  reply	other threads:[~2006-06-19 21:10 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
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 [this message]
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=200606200910.41974.manningc2@actrix.gen.nz \
    --to=manningc2@actrix.gen.nz \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=posaune@hotmail.com \
    --cc=tglx@linutronix.de \
    /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