Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 1 Feb 2003 13:41:59 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 1 Feb 2003 13:41:59 -0500 Received: from ip-161-71-171-238.corp-eur.3com.com ([161.71.171.238]:24314 "EHLO columba.www.eur.3com.com") by vger.kernel.org with ESMTP id ; Sat, 1 Feb 2003 13:41:58 -0500 X-Lotus-FromDomain: 3COM From: "Jon Burgess" To: linux-kernel@vger.kernel.org Message-ID: <80256CC0.0067A8CA.00@notesmta.eur.3com.com> Date: Sat, 1 Feb 2003 18:51:17 +0000 Subject: [RFC] Little endian Cramfs on big endian machines? Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At the moment the cramfs code in 2.4 & 2.5 uses the native machine endianness for the filesystem layout. I believe this behaviour has been considered a bug and that the code changed such that the filsystem is always little endian. There is some code in CVS at http://sourceforge.net/projects/cramfs which implements this for 2.4. I tried it a couple of months ago and it seemed OK, but it breaks backwards compatibility with old filesystems on big endian systems so I suspect it would never be done in a stable kernel series like 2.4. Should these changes be merged into 2.5? Jon - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/