linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: okorpil@fh-landshut.de
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Initrd and PPCbug, can it work?
Date: Mon, 26 Apr 2004 15:09:44 -0700	[thread overview]
Message-ID: <20040426220944.GI19246@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0404211503050.20798@ppcproject1>


On Wed, Apr 21, 2004 at 03:16:09PM +0200, okorpil@fh-landshut.de wrote:

> Hello!
>
> Target hardware: MVME2100, MPC8240 microcontroller - PowerPC 603e CPU
[snip]
> Is this even possible with the PPCbug, or do I need a Linux-friendly
> bootloader? I initially guessed, that if at bootup everything is
> relocated, that would actually suffice, and no additional information from
> the bootloader is required??

It works from PPCBug.  At least with cramfs, I _believe_ there is, or
has been a problem with creating an image on an LE machine for a BE
machine, and vice versa.  What happens when you try and use an ext2
ramdisk?

--
Tom Rini
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2004-04-26 22:09 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 [this message]
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
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=20040426220944.GI19246@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --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).