linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Michael Holzt <kju@fqdn.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Bugs in 2.4.0-ac2 in ppc
Date: Sat, 6 Jan 2001 16:09:17 -0700	[thread overview]
Message-ID: <20010106160917.K556@opus.bloom.county> (raw)
In-Reply-To: <20010105210627.D1095@fqdn.org>; from kju@fqdn.org on Fri, Jan 05, 2001 at 09:06:28PM +0100

[-- Attachment #1: Type: text/plain, Size: 347 bytes --]

On Fri, Jan 05, 2001 at 09:06:28PM +0100, Michael Holzt wrote:

>  - And third the worst problem: Since one of the latest test series
>    kernels i'm unable to use modules:

Ok, the attached patch (going into the 2_4 and 2_5 bk trees, so it will
eventually hit Linus or Alan) should fix it.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

[-- Attachment #2: modules.diff --]
[-- Type: text/plain, Size: 1381 bytes --]

===== arch/ppc/kernel/Makefile 1.1 vs edited =====
--- 1.1/arch/ppc/kernel/Makefile	Sat Jan  6 00:30:07 2001
+++ edited/arch/ppc/kernel/Makefile	Sat Jan  6 16:00:25 2001
@@ -35,6 +35,7 @@
 					process.o signal.o bitops.o ptrace.o \
 					ppc_htab.o semaphore.o syscalls.o  \
 					align.o setup.o
+obj-$(CONFIG_MODULES)		+= ppc_ksyms.o
 obj-$(CONFIG_POWER4)		+= xics.o
 obj-$(CONFIG_PCI)		+= pci.o pci-dma.o
 obj-$(CONFIG_KGDB)		+= ppc-stub.o
@@ -62,8 +63,7 @@
 					feature.o pmac_pci.o chrp_setup.o \
 					chrp_time.o chrp_pci.o 	open_pic.o \
 					indirect_pci.o i8259.o prep_pci.o \
-					prep_time.o prep_nvram.o ppc_ksyms.o \
-					prep_setup.o
+					prep_time.o prep_nvram.o prep_setup.o
 obj-$(CONFIG_PMAC_BACKLIGHT)	+= pmac_backlight.o
 obj-$(CONFIG_GEMINI)		+= gemini_prom.o gemini_pci.o gemini_setup.o \
 					open_pic.o
===== arch/ppc/kernel/ppc_ksyms.c 1.2 vs edited =====
--- 1.2/arch/ppc/kernel/ppc_ksyms.c	Sat Jan  6 14:21:00 2001
+++ edited/arch/ppc/kernel/ppc_ksyms.c	Sat Jan  6 16:03:40 2001
@@ -337,9 +337,11 @@
 EXPORT_SYMBOL(next_mmu_context);
 EXPORT_SYMBOL(set_context);
 EXPORT_SYMBOL(mmu_context_overflow);
+#if !defined(CONFIG_8xx) && !defined(CONFIG_4xx)
 extern long *intercept_table;
-extern long *ret_from_intercept;
 EXPORT_SYMBOL(intercept_table);
+#endif
+extern long *ret_from_intercept;
 EXPORT_SYMBOL(ret_from_intercept);

 #ifdef CONFIG_MOL

      parent reply	other threads:[~2001-01-06 23:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-05 20:06 Bugs in 2.4.0-ac2 in ppc Michael Holzt
2001-01-06 17:45 ` Tom Rini
2001-01-06 23:09 ` Tom Rini [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=20010106160917.K556@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=kju@fqdn.org \
    --cc=linuxppc-dev@lists.linuxppc.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).