From: Christoph Hellwig <hch@infradead.org>
To: Andi Drebes <lists-receive@programmierforen.de>
Cc: Tomas M <tomas@slax.org>, linux-fsdevel@vger.kernel.org
Subject: Re: cramfs in big endian
Date: Wed, 7 Nov 2007 22:49:36 +0000 [thread overview]
Message-ID: <20071107224936.GA8517@infradead.org> (raw)
In-Reply-To: <200711072151.49032.lists-receive@programmierforen.de>
On Wed, Nov 07, 2007 at 09:51:48PM +0100, Andi Drebes wrote:
> Hi!
>
> > I would suggest you to use squashfs instead of cramfs.
> > First, it's newer, it's better, it's actively developed, it doesn't have any
> > limits like the bad cramfs.
> I'm developing a new linux based firmware for my router which uses cramfs.
> Switching to squashfs still needs some time. Meanwhile, I have to work with
> cramfs. As the router uses the big endian format and as my machine works with
> the little endian format, I'm unable to mount the router's filesystem images.
Making cramfs endianess-independent shouldn't be much work. Take a look
at the helpers in fs/ufs/swab.h and use them for every ondisk access in
cramfs. Drop me a not if you need some help.
next prev parent reply other threads:[~2007-11-07 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 21:16 cramfs in big endian Andi Drebes
2007-11-07 13:52 ` Tomas M
2007-11-07 20:51 ` Andi Drebes
2007-11-07 22:49 ` Christoph Hellwig [this message]
2007-11-08 18:10 ` Andi Drebes
2007-11-10 1:03 ` H. Peter Anvin
2007-11-10 15:13 ` Christoph Hellwig
2007-11-10 20:19 ` H. Peter Anvin
2007-11-10 20:26 ` Andi Drebes
2007-11-10 20:30 ` H. Peter Anvin
2007-11-11 10:20 ` Andi Drebes
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=20071107224936.GA8517@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lists-receive@programmierforen.de \
--cc=tomas@slax.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;
as well as URLs for NNTP newsgroup(s).