linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Drebes <lists-receive@programmierforen.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: Tomas M <tomas@slax.org>, linux-fsdevel@vger.kernel.org
Subject: Re: cramfs in big endian
Date: Thu, 8 Nov 2007 19:10:24 +0100	[thread overview]
Message-ID: <200711081910.25399.lists-receive@programmierforen.de> (raw)
In-Reply-To: <20071107224936.GA8517@infradead.org>

Hi!

> 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.
I already started working on this feature some time ago. I think I am able to 
mount cramfs images with another endianness. But all I have to test this are 
images that use LZO compression istead of deflate.

In the original post I was just asking somebody possessing a big endian 
machine to create an image in big endian / deflate format. This would help me 
a lot. Later, I want to add support for multiple compression algorithms.

Thanks so far,
	Andi

  reply	other threads:[~2007-11-08 18:10 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
2007-11-08 18:10       ` Andi Drebes [this message]
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=200711081910.25399.lists-receive@programmierforen.de \
    --to=lists-receive@programmierforen.de \
    --cc=hch@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).