linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: paulus@samba.org
Cc: ppc64-dev <linuxppc64-dev@ozlabs.org>, ppc-dev <linuxppc-dev@ozlabs.org>
Subject: [PATCH 9/9] powerpc: make iSeries boot
Date: Sat, 1 Oct 2005 00:14:39 +1000	[thread overview]
Message-ID: <20051001001439.2f04423d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20050930233602.138b6e27.sfr@canb.auug.org.au>

Now that we use the device tree, it helps to build it in.
It also helps to link the kernel at the correct address.

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---

 arch/powerpc/Kconfig       |    4 ++--
 arch/powerpc/Kconfig.debug |    2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

1b4c416e0cf237dce004392122db45eb22dbc416
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -317,7 +317,7 @@ config PPC_BPA
 
 config PPC_OF
 	bool
-	depends on PPC_MULTIPLATFORM	# for now
+	depends on PPC_MULTIPLATFORM || PPC_ISERIES
 	default y
 
 config XICS
@@ -836,7 +836,7 @@ endmenu
 if PPC64
 config KERNEL_START
 	hex
-	default "0xc0000000"
+	default "0xc000000000000000"
 endif
 
 source "net/Kconfig"
diff --git a/arch/powerpc/Kconfig.debug b/arch/powerpc/Kconfig.debug
--- a/arch/powerpc/Kconfig.debug
+++ b/arch/powerpc/Kconfig.debug
@@ -55,7 +55,7 @@ config BDI_SWITCH
 
 config BOOTX_TEXT
 	bool "Support for early boot text console (BootX or OpenFirmware only)"
-	depends PPC_OF
+	depends PPC_OF && !PPC_ISERIES
 	help
 	  Say Y here to see progress messages from the boot firmware in text
 	  mode. Requires either BootX or Open Firmware.

      parent reply	other threads:[~2005-09-30 14:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 13:36 [PATCH 0/9] more merge changes Stephen Rothwell
2005-09-30 13:44 ` [PATCH 1/9] ppc64 iseries: move some iSeries include files Stephen Rothwell
2005-09-30 13:49 ` [PATCH 2/9] powerpc: merge asm-offsets.c Stephen Rothwell
2005-09-30 13:52 ` [PATCH 3/9] powerpc: remove old vector.S files Stephen Rothwell
2005-09-30 13:55 ` [PATCH 4/9] powerpc: more cleanup of powerpc/kernel Stephen Rothwell
2005-09-30 13:56 ` [PATCH 5/9] powerpc: Move lparmap.c to powerpc/platforms Stephen Rothwell
2005-09-30 14:00 ` [PATCH 6/9] powerpc: merge idle_power4.S and fixup traps.c Stephen Rothwell
2005-09-30 20:52   ` Kumar Gala
2005-10-01  2:17     ` Stephen Rothwell
2005-10-01  3:28       ` Paul Mackerras
2005-10-01 11:37         ` [PATCH 6/9] powerpc: merge idle_power4.S and traps.c Stephen Rothwell
2005-10-01 12:30           ` Stephen Rothwell
2005-09-30 14:05 ` [PATCH 7/9] ppc64: simplify the build a little Stephen Rothwell
2005-10-01 11:40   ` Stephen Rothwell
2005-09-30 14:10 ` [PATCH 8/9] powerpc: make iSeries build Stephen Rothwell
2005-10-02  1:06   ` Segher Boessenkool
2005-09-30 14:14 ` Stephen Rothwell [this message]

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=20051001001439.2f04423d.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --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 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).