From: Segher Boessenkool <segher@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc64-dev@ozlabs.org,
Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>
Subject: Re: Merging ppc32 and ppc64
Date: Wed, 10 Aug 2005 12:15:09 +0200 [thread overview]
Message-ID: <c852c80b15c4a22ed26f5cbd9313b69d@kernel.crashing.org> (raw)
In-Reply-To: <17145.13414.996858.522127@cargo.ozlabs.ibm.com>
> It is already the case (and has always been the case) that you can't
> boot a vmlinux image directly from OF - there is always either or both
> of yaboot or a zImage wrapper in between anyway.
If you fix the ELF headers, you can boot a vmlinux directly
from OF just fine.
I agree getting rid of all that RELOC() stuff is a worthy goal;
I just hope there's a better way to do it...
Anyway, I'm not going to stand in you guys way -- please
just don't make it harder for me without reason, though.
Segher
next prev parent reply other threads:[~2005-08-10 10:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-03 3:07 Merging ppc32 and ppc64 Paul Mackerras
2005-08-03 5:48 ` Fwd: " Kumar Gala
2005-08-08 17:59 ` Joel Schopp
2005-08-08 23:48 ` Paul Mackerras
2005-08-09 13:09 ` Segher Boessenkool
2005-08-09 13:11 ` Geert Uytterhoeven
2005-08-09 13:30 ` Segher Boessenkool
2005-08-09 14:12 ` Kumar Gala
2005-08-09 14:47 ` Arnd Bergmann
2005-08-09 15:01 ` Kumar Gala
2005-08-09 16:21 ` Tom Rini
2005-08-09 17:41 ` Kumar Gala
2005-08-09 17:47 ` Tom Rini
2005-08-09 18:49 ` Kumar Gala
2005-08-09 15:16 ` Segher Boessenkool
2005-08-09 22:55 ` Paul Mackerras
2005-08-09 23:00 ` Kumar Gala
2005-08-10 10:15 ` Segher Boessenkool [this message]
2005-08-09 14:52 ` Olof Johansson
2005-08-09 22:48 ` Paul Mackerras
2005-08-10 10:51 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2005-08-04 2:37 Goodman, Brad
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=c852c80b15c4a22ed26f5cbd9313b69d@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.