From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Drebes Subject: Re: cramfs in big endian Date: Thu, 8 Nov 2007 19:10:24 +0100 Message-ID: <200711081910.25399.lists-receive@programmierforen.de> References: <200711062216.27156.lists-receive@programmierforen.de> <200711072151.49032.lists-receive@programmierforen.de> <20071107224936.GA8517@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Tomas M , linux-fsdevel@vger.kernel.org To: Christoph Hellwig Return-path: Received: from server001.webpack.hosteurope.de ([80.237.130.9]:44506 "EHLO server001.webpack.hosteurope.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760288AbXKHSKy (ORCPT ); Thu, 8 Nov 2007 13:10:54 -0500 In-Reply-To: <20071107224936.GA8517@infradead.org> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.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