All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russ Dill <Russ.Dill@asu.edu>
To: Eric DEJONC <eric.dejonc@thales-e-transactions.com>
Cc: linux-mtd@lists.infradead.org
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: reverse mkfs.jffs2
Date: 06 May 2003 08:26:45 -0700	[thread overview]
Message-ID: <1052234804.2996.3.camel@gobbles> (raw)
In-Reply-To: <3EB7AA75.7B0DACF5@thales-e-transactions.com>

On Tue, 2003-05-06 at 05:28, Eric DEJONC wrote:
> Well, thank you, I did not think to loopback, thats a great idea. I'm gonna
> test. the only little problem is  that the 10M jffs2 file should take a long
> time to be sent on the board via a serial port (the only one I can use).
> 

I don't think you caught on to what mtdram is. mtdram lets you create an
mtdblock device on you *HOST* system. you don't need to send it to your
board via serial.

> > > I was wondering if someone had already done a prog that reverse
> > > mkfs.jffs2?
> > >
> > > I'd like to open a jffs2 ramdisk made by someone else, but I don't have
> > > enough space on my flash disk. So I would like to open it, but from the
> > > host machine that doesn't handle  jffs2.
> >
> > Use one of mtdram or mtdblock and use that. You can make a block
> > device from your image with loopback. Should be enough, I guess.
> >
-- 
Russ Dill <Russ.Dill@asu.edu>

  reply	other threads:[~2003-05-06 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:12 reverse mkfs.jffs2 Eric DEJONC
2003-05-06 12:24 ` Jörn Engel
2003-05-06 12:28   ` Eric DEJONC
2003-05-06 15:26     ` Russ Dill [this message]
2003-05-06 12:49 ` David Woodhouse
2003-05-06 14:44   ` Eric DEJONC

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=1052234804.2996.3.camel@gobbles \
    --to=russ.dill@asu.edu \
    --cc=eric.dejonc@thales-e-transactions.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.