public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Stephen D. Cohen" <scohen@atlanticpositioners.com>
To: <linux-mtd@lists.infradead.org>
Subject: Corrupted DOC 2000 and Tools Building Problems
Date: Thu, 22 May 2003 12:46:34 -0400	[thread overview]
Message-ID: <001201c32081$b4e2d360$1d28a8c0@flpalmharbor> (raw)

Gang,

	I am using linux-2.4.20 on a National Geode based PC.  All worked well
until I tried to create a JFFS2 file system on the raw /dev/mtd0 slice.
Needless to say this scrogged the NFTL formatting on the DOC.  So I figured
I would just reformat it using the DOS utilities available from the
M-Systems web site.  Wrong - I get an "ERROR IPL block is bad, Error
formatting DOC" when I try to use it.  This is on a DOC that worked just
fine until I tried to build the JFFS2 file system.  Whoops.

	I have also tried to build the util sub-tree from the mtd CVS archive.
Unfortunately I get many errors on headers with undefined types.  In
particular, uint32_t is flagged in crc32.h.  There are several others that
cause trouble further down the build, particularly the list structures.  I
am sure others have run in to this and I am doing something simple and
stupid - any help is greatly appreciated.

	If anyone can suggest a method to revive my scrogged DOC, I will greatly
appreciate it.  Any additional information on building the tools will be
gravy.  Heck, a pointer to a recently compiled binary version of the toosl
for i386 alone would be worth its weight in bits.

Regards,

Steve

----------------
Stephen D. Cohen
Engineering Manager
Atlantic Positioning Systems
11528 53rd Street North
Clearwater, FL 33760
(727) 299-0150
fax: (727) 299-0804

             reply	other threads:[~2003-05-22 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 16:46 Stephen D. Cohen [this message]
2003-05-24  0:10 ` Corrupted DOC 2000 and Tools Building Problems Mark Meade

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='001201c32081$b4e2d360$1d28a8c0@flpalmharbor' \
    --to=scohen@atlanticpositioners.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