All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chuck Meade" <chuckmeade@mindspring.com>
To: <linux-mtd@lists.infradead.org>
Subject: DOC filesystem questions
Date: Wed, 6 Aug 2003 00:27:50 -0400	[thread overview]
Message-ID: <IIEEICKJLNEPBBDJICNGAEENDMAA.chuckmeade@mindspring.com> (raw)

I have a DiskOnChip device soldered onto a PowerPC target and
would appreciate if someone could verify if I am using the 
correct commands to put a filesystem on it.

Also I am concerned from what I have read in the archives about
the bad block table.  From what I see in the archives and in
Karim Yaghmour's book, I needed to save this off.  Unfortunately
however I cannot run DOS or its utilities on this target board,
so I don't think that there is any way to do this.

I use the following commands:

  nftl_format /dev/mtd0
  fdisk /dev/nftla

(I know it's unnecessary for now to use partitioning when I just
have 1 partition, but I may be using multiple partitions in the
near future)

  mkfs.ext3 /dev/nftla1
  mount /dev/nftla1 /mnt

This filesystem on the DOC looks like it is working well.

 Questions:

1. Have I destroyed any bad block table in the device by
   doing this command sequence?

2. If so, is this a bad block table needed by firmware
   internal to the DOC, or just needed by some DOS utilities
   that I won't be using anyway?

3. What I would really prefer to use is JFFS2 on this DOC.
   I have seen messages from David that this may now be 
   possible.
   When I use other targets with NOR flash I typically write
   an MTD partition map file for the target, then I use dd to
   put my jffs2 image file into the right mtdblock partition.
   How would I do this with a DOC device?
   (Meaning how do you specify the MTD partition map for your
   DOC so you are able to specify /dev/mtdblock3, for example,
   as a destination for the fs image).

Thanks very much,
Chuck Meade

             reply	other threads:[~2003-08-06  4:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  4:27 Chuck Meade [this message]
2003-08-07 10:43 ` DOC filesystem questions David Woodhouse
2003-08-07 16:09   ` Chuck Meade
2003-08-07 16:32     ` David Woodhouse
2003-08-07 16:56       ` Chuck Meade
2003-08-08  7:30         ` David Woodhouse
2003-08-08 13:42           ` Chuck Meade
2003-08-08 14:05             ` David Woodhouse
2003-09-19 22:27           ` Chuck Meade
2003-09-20  1:20             ` Chuck 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=IIEEICKJLNEPBBDJICNGAEENDMAA.chuckmeade@mindspring.com \
    --to=chuckmeade@mindspring.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.