Cramfs Endianness

Brad (prettygood@cs.stanford.edu)
Wed, 26 Sep 2001 16:55:24 -0700 (PDT)


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)

Thanks,
Brad

-
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/