From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: [ANN] Squashfs 3.0 released
Date: Fri, 17 Mar 2006 11:00:40 -0500
Message-ID: <441ADD28.3090303@garzik.org>
References: <B6C8687D-6543-42A1-9262-653C4D3C30B2@lougher.org.uk> <20060317104023.GA28927@wohnheim.fh-wedel.de> <C91BFAB7-C442-4EB7-8089-B55BB86EB148@lougher.org.uk> <20060317124310.GB28927@wohnheim.fh-wedel.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1;
	format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE
Cc: Phillip Lougher <phillip@lougher.org.uk>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Return-path: <linux-kernel-owner+glk-linux-kernel-3=40m.gmane.org-S1751286AbWCQQA4@vger.kernel.org>
To: =?ISO-8859-1?Q?J=F6rn_Engel?= <joern@wohnheim.fh-wedel.de>
In-Reply-To: <20060317124310.GB28927@wohnheim.fh-wedel.de>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

J=F6rn Engel wrote:
> On Fri, 17 March 2006 11:16:48 +0000, Phillip Lougher wrote:
>=20
>>>The one still painfully missing is a
>>>fixed-endianness disk format.
>>
>>We had that argument last year.
>=20
>=20
> Yes, I remember.  What I don't remember is your opinion on the matter=
=2E
> Did we reach some sort of conclusion?

=46ixed endian isn't necessarily a requirement.  Detectable endian is. =
 As=20
long as (a) the filesystem mkfs notes the endian-ness and (b) the kerne=
l=20
filesystem code properly handles both types of endian, life is fine.

=46or SquashFS, though, I would think that fixed endian would be easy.=20
Since it is byte-packed, just handle endian as you unpack.

	Jeff