From: Tom Rini <trini@kernel.crashing.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sam Ravnborg <sam@ravnborg.org>,
Paul Mackerras <paulus@samba.org>
Subject: [PATCH][RESEND] Fix booting on a number of Motorola PPC32 machines
Date: Mon, 8 Dec 2003 08:19:19 -0700 [thread overview]
Message-ID: <20031208151919.GX912@stop.crashing.org> (raw)
In-Reply-To: <20031203163526.GH912@stop.crashing.org>
Hello. I first sent this on 3 Dec 2003, with no response or followup.
Currently a number of Motorola PPC32 machine will not boot, as
the final zImage isn't built correctly for them. The problem is that
we end up setting a Makefile variable to ' y' instead of 'y'. After
talking with Sam Ravnborg, the following is acceptable.
===== arch/ppc/boot/simple/Makefile 1.23 vs edited =====
--- 1.23/arch/ppc/boot/simple/Makefile Mon Sep 15 01:01:24 2003
+++ edited/arch/ppc/boot/simple/Makefile Mon Dec 1 12:25:29 2003
@@ -73,9 +73,8 @@
cacheflag-$(CONFIG_K2) := -include $(clear_L2_L3)
# kconfig 'feature', only one of these will ever be 'y' at a time.
-# The rest will be unset.
-motorola := $(CONFIG_MCPN765)$(CONFIG_MVME5100)$(CONFIG_PRPMC750) \
-$(CONFIG_PRPMC800)$(CONFIG_LOPEC)$(CONFIG_PPLUS)
+# The rest will be unset. Each of these must be on one line.
+motorola := $(CONFIG_MCPN765)$(CONFIG_MVME5100)$(CONFIG_PRPMC750)$(CONFIG_PRPMC800)$(CONFIG_LOPEC)$(CONFIG_PPLUS)
pcore := $(CONFIG_PCORE)$(CONFIG_POWERPMC250)
zimage-$(motorola) := zImage-PPLUS
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2003-12-08 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-03 16:35 [PATCH] Fix booting on a number of Motorola PPC32 machines Tom Rini
2003-12-08 15:19 ` Tom Rini [this message]
2003-12-15 16:51 ` [PATCH][RESEND x 2] " Tom Rini
2003-12-15 17:14 ` Keith Owens
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=20031208151919.GX912@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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).