linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Zhou" <zjzhou@newrocktech.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Problem on unresolved symbol
Date: Thu, 18 Sep 2003 12:00:20 +0800	[thread overview]
Message-ID: <000501c37d99$618e9b70$9702a8c0@newrock2> (raw)
In-Reply-To: <001601c37d51$019c2860$6401a8c0@sazabimobile>


Dear all,

In my driver, I use the request_8xxirq() to connect my ISR function to IRQ. Building is OK, but, when I use insmod to load this module into kernel, it report " unresolved symbol request_8xxirq ". I found that in fcc_enet.c, it also use request_8xxirq() to do. Why does my action unsuccessed ?

Could you help me?

Thanks in advance!
John

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

  reply	other threads:[~2003-09-18  4:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-17 19:22 EP405 and PCI and irq problem Shih-Ying Chou
2003-09-18  4:00 ` John Zhou [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-18 16:16 Problem on unresolved symbol Ming Lei

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='000501c37d99$618e9b70$9702a8c0@newrock2' \
    --to=zjzhou@newrocktech.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).