mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: prettygood@cs.stanford.edu, linux-kernel@vger.kernel.org
Subject: Re: Cramfs Endianness
Date: Sun, 30 Sep 2001 22:05:23 +0200	[thread overview]
Message-ID: <20010930220523.B186@bug.ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.33.0109261640310.19715-100000@earth.ayrnetworks.com>
In-Reply-To: <Pine.LNX.4.33.0109261640310.19715-100000@earth.ayrnetworks.com>; from Brad on Wed, Sep 26, 2001 at 04:55:24PM -0700

Hi!

> Although the documentation states that always going with little endian is
> the easiest solution and what was "decided" on, neither the kernel nor
> mkcramfs swabs on a big endian machine.  This is decidedly a problem with
> what we're doing, so I wrote a patch to swab the easy and not-quite-so-easy
> bitfields such that mkcramfs writes little endian images and the kernel
> swabs (if byteorder is defined as big_endian or __MIPSEB__ is defined)..
> It looks at the magic to determine whether to swab or not.
> 
> We've needed this, so we will have to incorporate this into a parallel
> repository if not added to the kernel.  Is there another solution afoot,
> or might I submit this patch? (please cc me if you respond)

Just submit the patch.

								Pavel
				...whose mips box is fortunately
					little endian...

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org

      reply	other threads:[~2001-10-01 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 23:55 Brad
2001-09-30 20:05 ` Pavel Machek [this message]

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=20010930220523.B186@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prettygood@cs.stanford.edu \
    /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

Powered by JetHome