public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting big endian jffs2 images on mtdram on a x86
Date: Mon, 14 May 2007 13:34:52 +0300	[thread overview]
Message-ID: <1179138892.3642.5.camel@sauron> (raw)
In-Reply-To: <1179133533.21753.13.camel@localhost.localdomain>

On Mon, 2007-05-14 at 11:05 +0200, Hans-Christian Egtvedt wrote:
> Hello,
> 
> I am trying to mount an JFFS2 image made with mkfs.jffs2 on my x86
> laptop. The image is made with --big-endian set.

I think you cannot do this without re-compiling JFFS2. I am not sure,
just glance to the code (to je32_to_cpu and the like macros).

> I do the following:
> modprobe mtdram total_size=8192 erase_size=64
> modprobe mtdchar
> modprobe mtdblock
> modprobe jffs2
> dd if=jffs2.image of=/dev/mtd0
> mount -t jffs2 /dev/mtdblock0 /some/mount/point

FYI, mtdblock is not needed and is ancient and confusing way to mount
jffs2. 

http://www.linux-mtd.infradead.org/faq/jffs2.html#L_mtdblock

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

  reply	other threads:[~2007-05-14 10:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-14  9:05 Mounting big endian jffs2 images on mtdram on a x86 Hans-Christian Egtvedt
2007-05-14 10:34 ` Artem Bityutskiy [this message]
2007-05-14 10:49   ` Haavard Skinnemoen
2007-05-14 14:37   ` Hans-Christian Egtvedt
2007-05-14 14:53     ` Josh Boyer
2007-05-15  0:42   ` David Woodhouse
2007-05-15  7:45     ` Hans-Christian Egtvedt
2007-05-15  7:50       ` Artem Bityutskiy
2007-05-15 10:07         ` Hans-Christian Egtvedt
2007-05-15  7:51       ` David Woodhouse
2007-05-16  7:45       ` MikeW
2007-05-16  8:02         ` Hans-Christian Egtvedt

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=1179138892.3642.5.camel@sauron \
    --to=dedekind@infradead.org \
    --cc=hcegtvedt@norway.atmel.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