From: Wolfgang Denk <wd@denx.de>
To: Marco Schramel <Schramel.Linux@go.bartec.de>
Cc: "PPC_LINUX" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: insmod trouble
Date: Tue, 25 May 2004 11:55:49 +0200 [thread overview]
Message-ID: <20040525095554.A5EC4C109F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Tue, 25 May 2004 11:05:11 +0200." <200405251105.11689.Schramel.Linux@go.bartec.de>
In message <200405251105.11689.Schramel.Linux@go.bartec.de> you wrote:
>
> My MPC8270 system works with 2.4.26 (toolchain ELDK), for development i use NFS (opt/eldk/ppc_82xx as rootfs). Now i write a device driver and have some trouble.
> I ve searched the whole list, but i didn't found some helpfully comments.
>
> --------------------------------------------------
> bash-2.05b# insmod demodriver.o
> demodriver.o: unresolved symbol module_unregister_chrdev
> demodriver.o: unresolved symbol register_chrdev
> demodriver.o: unresolved symbol led_init
> demodriver.o: unresolved symbol printf
> demodriver.o: unresolved symbol printk
> ------------------------------------------------
>
> What is the reason for this messages ??
The reason is bugs in your driver code.
module_unregister_chrdev - there is no such function in the Linux kernel.
Do you mean unregister_chrdev() or devfs_unregister_chrdev()?
led_init - there is no such exported kernel symbol. Which function
are you trying to call? Is this something in your own driver?
printk - there is no such function in the Linux kernel. Did you mean
printk() instead?
register_chrdev, printk - I can only speculate. These are exported
kernel symbols. probably you compile the driver with bad or
incomplete compiler options?
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Horses just naturally have mohawk haircuts.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-05-25 9:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 9:05 insmod trouble Marco Schramel
2004-05-25 9:55 ` Wolfgang Denk [this message]
2004-05-25 11:30 ` Zusatz zuRe: " Marco Schramel
2004-05-27 7:15 ` Marco Schramel
-- strict thread matches above, loose matches on Subject: below --
2004-04-02 0:17 Insmod trouble Rune Torgersen
2004-04-02 6:42 ` Marc Leeman
2004-04-02 16:54 ` Wolfgang Denk
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=20040525095554.A5EC4C109F@atlas.denx.de \
--to=wd@denx.de \
--cc=Schramel.Linux@go.bartec.de \
--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).