From: Joshua Kwan <joshk@triplehelix.org>
To: sparclinux@vger.kernel.org
Subject: [PATCH] export more symbols on sparc32
Date: Fri, 27 Aug 2004 19:41:07 +0000 [thread overview]
Message-ID: <cgo2on$h2$1@sea.gmane.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 380 bytes --]
Hello,
this patch against 2.6.8.1 exports a bunch of symbols that allow our
highly modular configs to work.
Now, re: the pci hunk, it may not be worth applying; a better solution
might be to turn off PCI for sparc32.. I have never seen a PCI-gifted
sparc32 but the config is largely an 'allmodconfig' and I decided to
just see what would happen.
Comments?
--
Joshua Kwan
[-- Attachment #1.2: sparc32-export-more-ksyms.dpatch --]
[-- Type: text/plain, Size: 914 bytes --]
# DP: export more symbols for sparc32 so we can get our stuff built
# DP: upstream-status: unsent
--- kernel-source-2.6.8/arch/sparc/kernel/sparc_ksyms.c~ 2004-08-27 01:09:06.000000000 -0700
+++ kernel-source-2.6.8/arch/sparc/kernel/sparc_ksyms.c 2004-08-27 01:10:27.000000000 -0700
@@ -214,6 +214,10 @@
EXPORT_SYMBOL(pci_dma_sync_single_for_device);
EXPORT_SYMBOL(pci_dma_sync_sg_for_cpu);
EXPORT_SYMBOL(pci_dma_sync_sg_for_device);
+EXPORT_SYMBOL(pci_map_sg);
+EXPORT_SYMBOL(pci_unmap_sg);
+EXPORT_SYMBOL(pci_map_page);
+EXPORT_SYMBOL(pci_unmap_page);
/* Actually, ioremap/iounmap are not PCI specific. But it is ok for drivers. */
EXPORT_SYMBOL(ioremap);
EXPORT_SYMBOL(iounmap);
@@ -298,6 +302,9 @@
/* Cache flushing. */
EXPORT_SYMBOL(sparc_flush_page_to_ram);
+/* For when serial stuff is built as modules. */
+EXPORT_SYMBOL(sun_do_break);
+
EXPORT_SYMBOL(__ret_efault);
EXPORT_SYMBOL(memcmp);
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 894 bytes --]
next reply other threads:[~2004-08-27 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 19:41 Joshua Kwan [this message]
2004-08-27 20:12 ` [PATCH] export more symbols on sparc32 David S. Miller
2004-08-27 21:20 ` C.Newport
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='cgo2on$h2$1@sea.gmane.org' \
--to=joshk@triplehelix.org \
--cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.