public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dzuy Nguyen <dzuy@infinity-studios.com>
To: linux-mtd@lists.infradead.org
Subject: mtd device clarification
Date: Wed, 20 Mar 2002 10:56:29 -0600	[thread overview]
Message-ID: <3C98BF3D.7030006@infinity-studios.com> (raw)

Can someone clarify what these device files are:

/dev/mtd*
/dev/mtdblock*
/dev/nftla*

I have a 16MB DoC.  My plan is to store a compressed root FS on the DoC 
flash and run the OS from
ramdisk.  I've erase the entire DoC, nftl_format the latter half of the 
DoC, make an ext2 FS on it,
and copy the kernel there.  I put my compressed root FS onto the flash 
section (first 8MB) with a
1024 offset:

# dd if=rootfs.gz of=/dev/mtd0 bs=1k seek=1024

I then tell the kernel where to get the rootfs

# rdev -r <kernel> 17408
# rdev <kernel> /dev/<which device file here?>

I've tried /dev/ramdisk, /dev/nftla and the kernel complains that it 
"Couldn't find valid RAM disk image
at 1024".
I've tried /dev/mtdblock0 (as in HOWTO) and I get I/O error from 
end_request.

I've read the bootdisk HOWTO (for /dev/fd0) and I think I can do the 
same for the DoC if I can just tell
the kernel where to get the compressed root FS.  Thanks for any advice.

Dzuy

                 reply	other threads:[~2002-03-20 16:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3C98BF3D.7030006@infinity-studios.com \
    --to=dzuy@infinity-studios.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