From: Matthew Locke <mlocke@mvista.com>
To: Steven Hein <ssh@sgi.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: mkcramfs changes to switch endianness
Date: Wed, 02 May 2001 13:39:07 -0700 [thread overview]
Message-ID: <3AF0706B.AB26C573@mvista.com> (raw)
In-Reply-To: 3AF07046.3827B997@sgi.com
cramfs is still endian dependant. Linus has a couple solutions to this
problem, but last time I checked he wasn't clear which was the best. go
for it and let us know how it turns out.
Steven Hein wrote:
>
> I'm getting ready to try using cramfs in the 2.4.4 kernel.
> Anybody done the work to make 'mkcramfs' create a big-endian
> image on a little-endian PC? Before I reinvent the wheel,
> I'd like to find out if anybody as done it (and would like
> to share :)
>
> Steve
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-02 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 20:38 mkcramfs changes to switch endianness Steven Hein
2001-05-02 20:39 ` Matthew Locke [this message]
2001-05-02 23:56 ` David Blythe
2001-05-03 2:24 ` Steve Hein
2001-05-03 18:32 ` David Blythe
2001-05-03 18:48 ` Matthew Locke
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=3AF0706B.AB26C573@mvista.com \
--to=mlocke@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=ssh@sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).