From: Hans-Christian Egtvedt <hcegtvedt@norway.atmel.com>
To: dedekind@infradead.org
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: Mounting big endian jffs2 images on mtdram on a x86
Date: Tue, 15 May 2007 12:07:02 +0200 [thread overview]
Message-ID: <1179223622.21753.46.camel@localhost.localdomain> (raw)
In-Reply-To: <1179215437.3642.8.camel@sauron>
On Tue, 2007-05-15 at 10:50 +0300, Artem Bityutskiy wrote:
> On Tue, 2007-05-15 at 09:45 +0200, Hans-Christian Egtvedt wrote:
> > 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.
>
> Sorry, I did not find an explanation what for do you need different
> endianess? Why not just to live with the default one?
I have a x86 laptop which i use for building my images, and deploy them
to an AVR32 system. Little endian vs. big endian.
Sometimes I would like to mount my jffs2 images to do some minor
modifications, fetch lost files, or if I receive an image from somebody
else.
--
Mvh
Hans-Christian Egtvedt
next prev parent reply other threads:[~2007-05-15 10:09 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
2007-05-15 7:50 ` Artem Bityutskiy
2007-05-15 10:07 ` Hans-Christian Egtvedt [this message]
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=1179223622.21753.46.camel@localhost.localdomain \
--to=hcegtvedt@norway.atmel.com \
--cc=dedekind@infradead.org \
--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