From: Oliver Korpilla <okorpil@fh-landshut.de>
To: Magnus Damm <damm@opensource.se>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Initrd and PPCbug, can it work?
Date: Tue, 27 Apr 2004 14:42:54 +0200 [thread overview]
Message-ID: <408E554E.3090801@fh-landshut.de> (raw)
In-Reply-To: <20040427124820.2f3aa14c.damm@opensource.se>
Magnus Damm wrote:
>>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.
>
Yeah, I see. But this may be the problem that I had the cramfs error
messages even with a cramfs initrd - this is endian sensitive and only
makes little-endian - won't work without a patch, so I really better
stick with ext2,hm?
Thanks,
Oliver Korpilla
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-04-27 12:42 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
2004-04-27 12:42 ` Oliver Korpilla [this message]
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=408E554E.3090801@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=damm@opensource.se \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).