From: John Bradford <john@grabjohn.com>
To: Jon_Burgess@eur.3com.com (Jon Burgess)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Little endian Cramfs on big endian machines?
Date: Sat, 1 Feb 2003 19:29:22 +0000 (GMT) [thread overview]
Message-ID: <200302011929.h11JTMiC010227@darkstar.example.net> (raw)
In-Reply-To: <80256CC0.0067A8CA.00@notesmta.eur.3com.com> from "Jon Burgess" at Feb 01, 2003 06:51:17 PM
> 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.
Maybe the native machine endianness is used for performace reasons -
that would make sense given the typical uses of cramfs. Also, it is a
read-only filesystem, so a userland application could flip the
endianness if a filesystem needs to be used on a non-native endianness
machine.
I'm not necessarily saying that that it's not a bug, just suggesting
an explaination.
John.
next prev parent reply other threads:[~2003-02-01 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 18:51 [RFC] Little endian Cramfs on big endian machines? Jon Burgess
2003-02-01 19:29 ` John Bradford [this message]
2003-02-01 21:27 ` Jörn Engel
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=200302011929.h11JTMiC010227@darkstar.example.net \
--to=john@grabjohn.com \
--cc=Jon_Burgess@eur.3com.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.