From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: cramfs in big endian Date: Wed, 7 Nov 2007 22:49:36 +0000 Message-ID: <20071107224936.GA8517@infradead.org> References: <200711062216.27156.lists-receive@programmierforen.de> <4731C308.8090008@slax.org> <200711072151.49032.lists-receive@programmierforen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Tomas M , linux-fsdevel@vger.kernel.org To: Andi Drebes Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:42750 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752792AbXKGWto (ORCPT ); Wed, 7 Nov 2007 17:49:44 -0500 Content-Disposition: inline In-Reply-To: <200711072151.49032.lists-receive@programmierforen.de> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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.