linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Magnus Damm <damm@opensource.se>
To: Oliver Korpilla <okorpil@fh-landshut.de>
Cc: mgroeger@sysgo.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Initrd and PPCbug, can it work?
Date: Tue, 27 Apr 2004 12:48:20 +0200	[thread overview]
Message-ID: <20040427124820.2f3aa14c.damm@opensource.se> (raw)
In-Reply-To: <408E2AF4.2050907@fh-landshut.de>


On Tue, 27 Apr 2004 11:42:12 +0200
Oliver Korpilla <okorpil@fh-landshut.de> wrote:

> This was the first I checked - CONFIG_EXT2_FS is set to y. Besides, I
> tried doing the same with a cramfs initrd - won't work either. Cannot
> say whether I configured that right.
>
> Maybe this is an endianess problem in my initrds?

As long as you use ext2 you should not have any endian problems.

It might be tempting to use other fancy filesystems, but I don't
like endian problems so I usually stick to ext2. I create my
ext2 initrds on x86 systems and use them on ppc without problems.

/ magnus

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2004-04-27 10:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-21 13:16 Initrd and PPCbug, can it work? okorpil
2004-04-26 22:09 ` Tom Rini
2004-04-27  6:39   ` Oliver Korpilla
2004-04-27  7:18     ` Marius Groeger
2004-04-27  8:50       ` Oliver Korpilla
2004-04-27  9:22         ` Marius Groeger
2004-04-27  9:42           ` Oliver Korpilla
2004-04-27 10:48             ` Magnus Damm [this message]
2004-04-27 12:42               ` Oliver Korpilla
2004-04-27 11:13             ` Marius Groeger
2004-04-27 12:45               ` Oliver Korpilla
2004-04-27 13:39                 ` Magnus Damm
2004-04-27 16:17                   ` Different solution Oliver Korpilla
2004-04-28  7:28                   ` Oliver Korpilla

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=20040427124820.2f3aa14c.damm@opensource.se \
    --to=damm@opensource.se \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=mgroeger@sysgo.com \
    --cc=okorpil@fh-landshut.de \
    /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;
as well as URLs for NNTP newsgroup(s).