From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Cc: Marcelo Tossati <marcelo@conectiva.com.br>
Subject: [PATCH] Alpha-Nautilus compilation fix for 2.4.17rc2
Date: Wed, 19 Dec 2001 20:24:30 -0700 [thread overview]
Message-ID: <20011219202430.A8610@mail.harddata.com> (raw)
To compile 2.4.17rc2 sources on Alpha not "generic" but Nautilus-specic,
or for any other Alpha type where Irongate chipset is used, the
following obvious patch is required:
--- linux-2.4.17rc/arch/alpha/kernel/alpha_ksyms.c.orig Tue Nov 20 16:49:31 2001
+++ linux-2.4.17rc/arch/alpha/kernel/alpha_ksyms.c Wed Dec 19 19:21:02 2001
@@ -258,3 +258,8 @@
EXPORT_SYMBOL_NOVERS(memchr);
EXPORT_SYMBOL(get_wchan);
+
+#ifdef CONFIG_ALPHA_IRONGATE
+EXPORT_SYMBOL(irongate_ioremap);
+EXPORT_SYMBOL(irongate_iounmap);
+#endif
Without it assorted modules will be really unhappy with depmod spilling
"unresolved symbols".
Actually the same patch applies to at least 2.4.16 and possibly earlier
kernels. With "generic" kernel configuration 'ioremap' and 'iounmap'
are not redefined in headers to their "irongate" variants and problem
does not occur.
Michal
michal@harddata.com
reply other threads:[~2001-12-20 3:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20011219202430.A8610@mail.harddata.com \
--to=michal@harddata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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