> > > 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?
Because you want to be able to mount cramfs from your devel machine.
Or imagine putting cramfs on a CD.
Pavel
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.- 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/