Re: [PATCH] Endianness-aware mkcramfs

[Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>]

On Tue, Dec 04, 2001 at 10:42:51AM -0800, H. Peter Anvin wrote:
> > As told above, it could be cleaner, but I don't know of a nice method of
> > accessing byteorder dependent data through structures.
> 
> This isn't the right way to deal with this.  The right way to deal
> with this is to get all systems to read cramfs the same way.

Yes, from a CS point of view. 

But practically cramfs is created once to contain some kind of
ROM for embedded devices. So if we never modify these data again,
why not creating it in the required byte order? 

Why wasting kernel cycles for le<->be conversion? Just because
it's more general? For writable general purpose file systems it
makes sense, but to none of romfs, cramfs etc.

So I would prefer the given patch.

Regards

Ingo Oeser
-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth