From: tony@bakeyournoodle.com (Tony Breeds)
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bret Towe <magnade@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: 2.6.22-git ppc build failure
Date: Wed, 18 Jul 2007 16:17:48 +1000 [thread overview]
Message-ID: <20070718061748.GZ10345@bakeyournoodle.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0707171927110.27353@woody.linux-foundation.org>
On Tue, Jul 17, 2007 at 07:27:51PM -0700, Linus Torvalds wrote:
> Ok, thanks. Maybe it's the merge, and maybe it's one of the sides. You
> might want to double-check that both parents are ok before you look too
> closely at the merge itself.
Turns out the boot failure wasn't related to the merge after all. With
my orginal compile (and the revert below) PCI works and the kernel
boots.
Please apply both.
From: Tony Breeds <tony@bakeyournoodle.com>
Subject: [PATCH] Revert "[POWERPC] Do firmware feature fixups after features are initialised"
This reverts commit 5a26f6bbb767d7ad23311a1e81cfdd2bebefb855.
The original patch causes boot failures when built with ppc64_defconfig. The
quickest fix is to revert it while alterates are investigated.
Signed-off-by: Tony Breeds <tony@bakeyournoodle.com>
---
arch/powerpc/kernel/setup_64.c | 12 ++++--------
1 files changed, 4 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/kernel/setup_64.c b/arch/powerpc/kernel/setup_64.c
index bc43bba..6018178 100644
--- a/arch/powerpc/kernel/setup_64.c
+++ b/arch/powerpc/kernel/setup_64.c
@@ -350,11 +350,13 @@ void __init setup_system(void)
{
DBG(" -> setup_system()\n");
- /* Apply CPUs-specific fixups to kernel text (nop out sections
- * not relevant to this CPU)
+ /* Apply the CPUs-specific and firmware specific fixups to kernel
+ * text (nop out sections not relevant to this CPU or this firmware)
*/
do_feature_fixups(cur_cpu_spec->cpu_features,
&__start___ftr_fixup, &__stop___ftr_fixup);
+ do_feature_fixups(powerpc_firmware_features,
+ &__start___fw_ftr_fixup, &__stop___fw_ftr_fixup);
/*
* Unflatten the device-tree passed by prom_init or kexec
@@ -392,12 +394,6 @@ void __init setup_system(void)
if (ppc_md.init_early)
ppc_md.init_early();
- /* Apply firmware specific fixups to kernel text (nop out
- * sections not relevant to this firmware)
- */
- do_feature_fixups(powerpc_firmware_features,
- &__start___fw_ftr_fixup, &__stop___fw_ftr_fixup);
-
/*
* We can discover serial ports now since the above did setup the
* hash table management for us, thus ioremap works. We do that early
--
1.5.2.3
Yours Tony
linux.conf.au http://linux.conf.au/ || http://lca2008.linux.org.au/
Jan 28 - Feb 02 2008 The Australian Linux Technical Conference!
next prev parent reply other threads:[~2007-07-18 6:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 18:04 Bret Towe
2007-07-18 1:03 ` [PATCH] " Tony Breeds
2007-07-18 1:44 ` Linus Torvalds
2007-07-18 2:24 ` Tony Breeds
2007-07-18 2:27 ` Linus Torvalds
2007-07-18 6:17 ` Tony Breeds [this message]
2007-07-18 17:02 ` Bret Towe
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=20070718061748.GZ10345@bakeyournoodle.com \
--to=tony@bakeyournoodle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®