From: "Brian S. Park" <brian@corelis.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: kernel modules and symbols
Date: Fri, 20 Jun 2003 13:48:40 -0700 [thread overview]
Message-ID: <5.1.1.6.2.20030620133837.0131da68@corelis.com> (raw)
Hi all,
I got Linux running on our custom board and am in the process of learning
how to build the final image to be burned on the flash.
To support our application I wrote simple device driver which maps the
physical address space to user space.
During development (NFS file system), it worked good enough. I could
install/un-install it without any problem using insmod/rmmod.
However, when I tried to install the module when using SELF ramdisk image,
I get bunch of unresolved symbols error.
What gives? I'm using exactly the same kernel so the symbols should be
there whether I use NFS root or SELF ram disk as root.
Any help will be appreciated.
# insmod FPGA_module
Using /lib/modules/2.4.20/FPGA_module.o
insmod: unresolved symbol remap_page_range
insmod: unresolved symbol create_proc_entry
insmod: unresolved symbol ioremap
insmod: unresolved symbol iounmap
insmod: unresolved symbol proc_mkdir
insmod: unresolved symbol remove_proc_entry
insmod: unresolved symbol sprintf
insmod: unresolved symbol printk
===============================================================
Brian S. Park brian@corelis.com (562) 926-6727 x143
---------------------------------------------------------------
Everything we do helps our customers get to market
FASTER with HIGHER quality and LOWER cost
===============================================================
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-06-20 20:48 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=5.1.1.6.2.20030620133837.0131da68@corelis.com \
--to=brian@corelis.com \
--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).