From: Jerome Glisse <j.glisse@gmail.com>
To: trini@kernel.crashing.org, linuxppc-dev@ozlabs.org,
linuxppc64-dev@ozlabs.org
Subject: Classic PPC specific ASM (CONFIG_6XX)
Date: Sun, 9 Jan 2005 16:40:56 +0100 [thread overview]
Message-ID: <4240b916050109074053e328b1@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 627 bytes --]
Hi,
With 2.6.10 i get a compilation error with disable_6xx_mmu
i guess this is linked with the patch you supplied in december
in arch/ppc/boot/common/util.S
Patch which comment disable_6xx_mmu if flags CONFIG_6XX
not defined. The problem arise in arch/ppc/boot/simple/misc-prep.c
where there is no conditional compilation for this function.
Attached is a patch that use the flags CONFIG_6XX to comment
out call to this function if flags not set.
By the way there is many compilation warning related to PPC with 2.6.10
anyone looking to correct them ?
Signed-off-by: Jerome Glisse <j.glisse@gmail.com>
best,
Jerome Glisse
[-- Attachment #2: disable_6xx-patch --]
[-- Type: application/octet-stream, Size: 855 bytes --]
diff -Nru linux/arch/ppc/boot/simple/misc-prep.c linux-2.6.10/arch/ppc/boot/simple/misc-prep.c
--- linux/arch/ppc/boot/simple/misc-prep.c 2004-12-24 22:33:51.000000000 +0100
+++ linux-2.6.10/arch/ppc/boot/simple/misc-prep.c 2005-01-09 16:30:59.938766448 +0100
@@ -34,7 +34,9 @@
extern void serial_fixups(void);
extern struct bi_record *decompress_kernel(unsigned long load_addr,
int num_words, unsigned long cksum);
+#ifdef CONFIG_6XX
extern void disable_6xx_mmu(void);
+#endif
extern unsigned long mpc10x_get_mem_size(void);
static void
@@ -152,9 +154,11 @@
hold_residual->VitalProductData.Reserved5 = 0xdeadbeef;
}
+ #ifdef CONFIG_6XX
/* Now go and clear out the BATs and ensure that our MSR is
* correct .*/
disable_6xx_mmu();
+ #endif
/* Make r3 be a pointer to the residual data. */
return (unsigned long)hold_residual;
next reply other threads:[~2005-01-09 15:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 15:40 Jerome Glisse [this message]
2005-01-09 21:03 ` Classic PPC specific ASM (CONFIG_6XX) Paul Mackerras
2005-01-10 14:52 ` Tom Rini
2005-01-10 16:39 ` Christoph Hellwig
2005-01-10 16:44 ` Tom Rini
2005-01-10 18:14 ` Jerome Glisse
2005-01-10 18:29 ` Tom Rini
2005-01-10 18:59 ` Jerome Glisse
2005-01-10 19:12 ` Tom Rini
2005-01-10 19:31 ` Jerome Glisse
[not found] ` <4240b91605011211101ed322a8@mail.gmail.com>
[not found] ` <20050120231442.GE2626@smtp.west.cox.net>
2005-01-21 11:22 ` Jerome Glisse
2005-01-21 12:36 ` Geert Uytterhoeven
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=4240b916050109074053e328b1@mail.gmail.com \
--to=j.glisse@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).