All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting big endian jffs2 images on mtdram on a x86
Date: Mon, 14 May 2007 16:37:25 +0200	[thread overview]
Message-ID: <1179153445.21753.29.camel@localhost.localdomain> (raw)
In-Reply-To: <1179138892.3642.5.camel@sauron>

On Mon, 2007-05-14 at 13:34 +0300, Artem Bityutskiy wrote:
> 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).

Oki, then I at least know where to look. It would have been a nice
feature to add support for choosing endianess when loading the module.

I would not recommend customers or less experienced Linux people to
recompile one of their kernel modules to support big endian JFFS2
images.

<cut jffs2 image mounting>

> > 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

Oh, thanks, and as Håvard stated it is also supported in the latest
busybox.

-- 
Mvh
Hans-Christian Egtvedt

  parent reply	other threads:[~2007-05-14 14:39 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
2007-05-14 10:49   ` Haavard Skinnemoen
2007-05-14 14:37   ` Hans-Christian Egtvedt [this message]
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=1179153445.21753.29.camel@localhost.localdomain \
    --to=hcegtvedt@norway.atmel.com \
    --cc=dedekind@infradead.org \
    --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.