public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: mark.langsdorf@amd.com
Cc: mtd@infradead.org
Subject: Re: Simple Newbie Questions for MTD and JFFS
Date: Fri, 25 Aug 2000 17:34:28 +0100	[thread overview]
Message-ID: <28611.967221268@cygnus.co.uk> (raw)
In-Reply-To: <0FA1031B65A9D111960900805F9FA8E103B9F080@txexmta8.amd.com>


mark.langsdorf@amd.com said:
>  If I copy a file directly into the mount point, it doesn't show up
> the next time I mount the flash.  If I use mkfs.jffs to create an
> image and copy that into flash, I can see the image but I can't access
> the files that I put into it. 

That's odd. Are you 100% sure that the physical write support for your 
flash chips is working? When you make an image with mkfs.jffs, how are you 
writing that to the flash?

You _are_ using the latest version from CVS, aren't you?


mark.langsdorf@amd.com said:
> I guess I'm asking if there's any documentation or hints on how to use
> the files in the util/ directory, 

Erase a single erase block in a device:
	erase <device> <offset>
e.g.:	erase /dev/mtd0 0

Erase a whole device:
	eraseall <device>
e.g.:	eraseall /dev/mtd0

Load an image into a device:
	doc_loadbios <device> <image>
e.g.:	doc_loadbios /dev/mtd0 myimage.jffs
 (note: This doesn't erase to the end of the device, only as far as is 
necessary to load the image. Use 'eraseall' beforehand if necessary)

> as well as how mtd and jffs are supposed to work once they've mounted. 

Once JFFS is mounted, it should just work. It does for me.


--
dwmw2




To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

      reply	other threads:[~2000-08-25 16:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-25 16:21 Simple Newbie Questions for MTD and JFFS mark.langsdorf
2000-08-25 16:34 ` David Woodhouse [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=28611.967221268@cygnus.co.uk \
    --to=dwmw2@infradead.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mtd@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