public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: DOC Mill Plus 32M  What next?
Date: Wed, 02 Jun 2004 00:34:34 +1000	[thread overview]
Message-ID: <40BC93FA.1010508@snapgear.com> (raw)
In-Reply-To: <1086097361.26119.213.camel@hades.cambridge.redhat.com>

David Woodhouse wrote:
> On Tue, 2004-06-01 at 09:39 -0400, Carlos, John J USAATC wrote:
> 
>>What tools can I use on the chip to prepare it for use??  Nftl_format
>>reports wrong erase size of 0x10000?  I have read others postings and I am
>>not sure if I should be using nftl_format anyway?  Can soemone please tell
>>me the proper procedure to prep the chip for a jffs2 file system???
> 
> 
> Use the DOS tools if you can. Or look on SnapGear's web site to see if
> you can find an 'inftl_format' tool. 

I keep an nftl_format in the uClinux-dist code base that is capable
of formating INFTL as well.

Get the whole package and use uClinux-dist/user/mtd-utils/nftl_format.c

http://www.uclinux.org/pub/uClinux/dist/

Or just pull it from CVS at:

http://cvs.uclinux.org/cgi-bin/cvsweb/uClinux-dist/user/mtd-utils/nftl_format.c

It doesn't currently support erase sizes of 0x10000 either though...

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Chief Software Dude       EMAIL:     gerg@snapgear.com
SnapGear -- a CyberGuard Company            PHONE:       +61 7 3435 2888
825 Stanley St,                             FAX:         +61 7 3891 3630
Woolloongabba, QLD, 4102, Australia         WEB: http://www.SnapGear.com

      reply	other threads:[~2004-06-01 14:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-01 13:39 DOC Mill Plus 32M What next? Carlos, John J USAATC
2004-06-01 13:42 ` David Woodhouse
2004-06-01 14:34   ` Greg Ungerer [this message]

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=40BC93FA.1010508@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=dwmw2@infradead.org \
    --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