mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Endianness-aware mkcramfs
Date: Thu, 6 Dec 2001 14:12:33 +0000	[thread overview]
Message-ID: <20011206141232.B122@toy.ucw.cz> (raw)
In-Reply-To: <3C0BD8FD.F9F94BE0@mvista.com> <3C0CB59B.EEA251AB@lightning.ch> <9uj5fbfm@cesium.transmeta.com> <20011205013630.C717@nightmaster.csn.tu-chemnitz.de>
In-Reply-To: <20011205013630.C717@nightmaster.csn.tu-chemnitz.de>; from ingo.oeser@informatik.tu-chemnitz.de on Wed, Dec 05, 2001 at 01:36:30AM +0100

Hi!

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


  parent reply	other threads:[~2001-12-06 20:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3C0BD8FD.F9F94BE0@mvista.com>
2001-12-04 11:38 ` Daniel Marmier
2001-12-04 18:42   ` H. Peter Anvin
2001-12-05  0:36     ` Ingo Oeser
2001-12-05  0:39       ` H. Peter Anvin
2001-12-05  0:49         ` Matthew Dharm
2001-12-05  1:02           ` Jeremy Puhlman
2001-12-05  1:12             ` H. Peter Anvin
2001-12-05  1:38             ` Matthew Dharm
2001-12-05 12:23               ` Daniel Marmier
2001-12-06  6:04                 ` H. Peter Anvin
2001-12-06 14:12       ` Pavel Machek [this message]
2001-12-18  2:52   ` Daniel Quinlan

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=20011206141232.B122@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=hpa@zytor.com \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®