public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Mounting big endian jffs2 images on mtdram on a x86
Date: Tue, 15 May 2007 09:45:26 +0200	[thread overview]
Message-ID: <1179215126.21753.40.camel@localhost.localdomain> (raw)
In-Reply-To: <1179189724.3482.24.camel@shinybook.infradead.org>

On Tue, 2007-05-15 at 08:42 +0800, David Woodhouse wrote:
> On Mon, 2007-05-14 at 13:34 +0300, Artem Bityutskiy wrote:
> > 
> > > 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).
> 
> Edit fs/jffs2/nodelist.h and set JFFS2_BIG_ENDIAN instead of
> JFFS2_NATIVE_ENDIAN.

Ah, thanks for this hint.

> The reason it's not a runtime option is because that would be quite
> slow, and it's a very esoteric feature.

For development systems it would be a great feature, hence my original
email. But for an embedded system this should not be present at all.

> I'm sorry. I should have just made it either big- or little-endian right
> from the very beginning and never made the mistake of letting it be
> host-endian.

What I would have liked was a possibility to choose which read/write
operations should be used when using my developing machine, but for the
kernel I boot my embedded target with I would like an optimized jffs2
driver.

Use native endianess by default, but have a possibility to override at
runtime.

</thoughts>

-- 
Best regards
Hans-Christian Egtvedt

  reply	other threads:[~2007-05-15  7:45 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
2007-05-14 14:53     ` Josh Boyer
2007-05-15  0:42   ` David Woodhouse
2007-05-15  7:45     ` Hans-Christian Egtvedt [this message]
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=1179215126.21753.40.camel@localhost.localdomain \
    --to=hcegtvedt@norway.atmel.com \
    --cc=dwmw2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox