linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joe Green <jgreen@mvista.com>
To: dony <dony.he@huawei.com.cn>, Dan Malek <dan@netx4.com>,
	linuxppc-embed <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Does mpc8xx-2.2.13 support "Enable loadable module support"?
Date: Tue, 21 Mar 2000 17:54:30 -0800	[thread overview]
Message-ID: <00032117584900.03592@minotaur.mvista.com> (raw)
In-Reply-To: <38D8236B.C27DE94B@huawei.com.cn>


On Tue, 21 Mar 2000, dony wrote:
>      If I compile the kernel without "Enable loadable module support" , then it
> works successfully. But if  I do again with "Enable loadable module support", then
> some errors occur:
> Does someone know why?

Here's a patch I believe should fix these problems.  Let me know if you
have any problems with it.  This is based on the Hard Hat Linux kernel
we ship, so there may be some differences from the tree you have (hope
not).

--- linux.old/arch/ppc/kernel/ppc8xx_pic.c	Tue Mar 21 02:03:06 2000
+++ linux/arch/ppc/kernel/ppc8xx_pic.c	Tue Mar 21 17:42:58 2000
@@ -148,4 +148,15 @@
 	irq += i8259_pic.irq_offset;
 	return (request_8xxirq(irq, handler, irqflags, devname, dev_id));
 }
-#endif
+#else /* CONFIG_MBX */
+int request_irq(
+	unsigned int irq,
+	void (*handler)(int, void *, struct pt_regs *),
+	unsigned long irqflags,
+	const char * devname,
+	void *dev_id
+)
+{
+	return -EINVAL;
+}
+#endif /* CONFIG_MBX */
--- linux.old/arch/ppc/kernel/ppc_ksyms.c	Wed Oct 20 00:14:00 1999
+++ linux/arch/ppc/kernel/ppc_ksyms.c	Tue Mar 21 18:31:02 2000
@@ -69,14 +69,18 @@
 EXPORT_SYMBOL(ppc_local_irq_count);
 EXPORT_SYMBOL(ppc_local_bh_count);

+#ifdef CONFIG_PCI
 EXPORT_SYMBOL(isa_io_base);
 EXPORT_SYMBOL(isa_mem_base);
 EXPORT_SYMBOL(pci_dram_offset);
+#endif /* CONFIG_PCI */
 EXPORT_SYMBOL(ISA_DMA_THRESHOLD);
 EXPORT_SYMBOL(DMA_MODE_READ);
 EXPORT_SYMBOL(DMA_MODE_WRITE);
+#ifndef CONFIG_8xx
 EXPORT_SYMBOL(_prep_type);
 EXPORT_SYMBOL(ucSystemType);
+#endif /* CONFIG_8xx */

 EXPORT_SYMBOL(atomic_add);
 EXPORT_SYMBOL(atomic_sub);
@@ -181,18 +185,21 @@
 EXPORT_SYMBOL(_machine);
 EXPORT_SYMBOL(ppc_md);

+#ifndef CONFIG_8xx
 EXPORT_SYMBOL(adb_request);
 EXPORT_SYMBOL(adb_register);
 EXPORT_SYMBOL(cuda_request);
 EXPORT_SYMBOL(cuda_poll);
 EXPORT_SYMBOL(pmu_request);
 EXPORT_SYMBOL(pmu_poll);
+#endif /* CONFIG_8xx */
 #ifdef CONFIG_PMAC_PBOOK
 EXPORT_SYMBOL(pmu_register_sleep_notifier);
 EXPORT_SYMBOL(pmu_unregister_sleep_notifier);
 EXPORT_SYMBOL(pmu_enable_irled);
 #endif CONFIG_PMAC_PBOOK
 EXPORT_SYMBOL(abort);
+#ifndef CONFIG_8xx
 EXPORT_SYMBOL(find_devices);
 EXPORT_SYMBOL(find_type_devices);
 EXPORT_SYMBOL(find_compatible_devices);
@@ -204,6 +211,7 @@
 EXPORT_SYMBOL(feature_set);
 EXPORT_SYMBOL(feature_clear);
 EXPORT_SYMBOL(feature_test);
+#endif /* CONFIG_8xx */
 #ifdef CONFIG_SCSI
 EXPORT_SYMBOL(note_scsi_host);
 #endif
@@ -214,7 +222,9 @@
 #endif /* CONFIG_PMAC */

 EXPORT_SYMBOL(abs);
+#ifndef CONFIG_8xx
 EXPORT_SYMBOL(device_is_compatible);
+#endif /* CONFIG_8xx */

 EXPORT_SYMBOL_NOVERS(__ashrdi3);
 EXPORT_SYMBOL_NOVERS(__lshrdi3);
--- linux.old/drivers/macintosh/Makefile	Thu Apr 29 19:53:48 1999
+++ linux/drivers/macintosh/Makefile	Tue Mar 21 18:21:04 2000
@@ -15,7 +15,7 @@
 L_TARGET := macintosh.a
 M_OBJS   :=

-ifndef CONFIG_MBX
+ifndef CONFIG_8xx
 L_OBJS   := via-cuda.o macio-adb.o via-pmu.o mediabay.o
 LX_OBJS  := adb.o
 endif


--
Joe Green <jgreen@mvista.com>
MontaVista Software, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-22  1:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 15:57 Question on QSPAN Driver Steve Rossi
2000-03-20 17:31 ` Dan Malek
2000-03-20 19:44   ` Steve Rossi
2000-03-20 20:03     ` Dan Malek
2000-03-21  2:07       ` Jason Wohlgemuth
2000-03-21  3:07         ` Dan Malek
2000-03-22  1:35           ` Does mpc8xx-2.2.13 support "Enable loadable module support"? dony
2000-03-22  1:54             ` Joe Green [this message]
2000-03-22  3:10               ` dony

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=00032117584900.03592@minotaur.mvista.com \
    --to=jgreen@mvista.com \
    --cc=dan@netx4.com \
    --cc=dony.he@huawei.com.cn \
    --cc=linuxppc-embedded@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).