Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Posnjak <simon@activetools.si>
To: Christopher Hoover <ch@murgatroid.com>
Cc: 'linux-mtd' <linux-mtd@lists.infradead.org>
Subject: RE: jffs, jffs2
Date: 25 Sep 2002 13:18:07 +0200	[thread overview]
Message-ID: <1032952690.2913.27.camel@klada.dyndns.org> (raw)
In-Reply-To: <001501c26404$40977630$7e00000a@bergamot>

On Tue, 2002-09-24 at 21:54, Christopher Hoover wrote:
> 
> Use jffs2 over jffs.
> 
> Caveat with 2.5: if your flash has variable-sized blocks (e.g. Intel C3
> flash), you'll need to either use the mtd CVS or patch the 2.5 sources
> accordingly. 
I wasn't to clear: I will be using 2.4.18. The date in TODO file which
is located in fs/jffs2 directory is 2001/03/01 which seams to be a bit
old. What I would like to now is there a newer (stable) version. (What
to pull out of the CVS - HEAD or some other taged version)

> Use mkfs.jffs2 to build the image.
> 
> With blob, just pretend "ramdisk" is "root".  You'll need to have
> configured the proper partitioning into both blob and the sa1100 mtd
> partition code. 
> 
> Write the image by doing "erase ramdisk; xdownload ramdisk; {send the
> file}; flash ramdisk".  The erase is important.    
> 
> One final thing: be sure to configure your blob parameters to tell it
> not to load the ramdisk automatically.  

OK I got this, thank you for your help. Just one more thing:

So to mount an empty mtd partition as jffs/jffs2 all I have to do is to
erase it (using erase utilty from mtd)and then just do mount -t jffs2
/dev/mtdblock5 /somedir. Is this correct?

	Regards Simon

  reply	other threads:[~2002-09-25 11:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24 18:41 jffs, jffs2 Simon Posnjak
2002-09-24 19:54 ` Christopher Hoover
2002-09-25 11:18   ` Simon Posnjak [this message]
2002-09-25 18:22     ` Christopher Hoover

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=1032952690.2913.27.camel@klada.dyndns.org \
    --to=simon@activetools.si \
    --cc=ch@murgatroid.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