From: Bill Gatliff <bgat@billgatliff.com>
To: Laurent Pinchart <laurent.pinchart@technotrade.biz>
Cc: Linuxppc-embedded@ozlabs.org
Subject: Re: Compiling interrupt controller code as a module
Date: Tue, 17 Apr 2007 12:13:24 -0500 [thread overview]
Message-ID: <46250034.7000202@billgatliff.com> (raw)
In-Reply-To: <200704171731.43608.laurent.pinchart@technotrade.biz>
Laurent Pinchart wrote:
> Hi everybody.
>
> I wrote a kernel driver for a custom bus (using arch/ppc). The hardware has a
> cascaded interrupt controller wired to one of the CPU interrupts. The
> interrupt controller IRQ handler calls __do_IRQ() to dispatch interrupts.
>
> Everything worked fine until I tried to compile the code as a module because
> __do_IRQ() is not exported. Is there a way to compile an interrupt controller
> as a module, or must it be included in the kernel ?
>
Could you just export __do_IRQ()?
b.g.
--
Bill Gatliff
bgat@billgatliff.com
next prev parent reply other threads:[~2007-04-17 17:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-17 15:31 Compiling interrupt controller code as a module Laurent Pinchart
2007-04-17 17:13 ` Bill Gatliff [this message]
2007-04-18 9:39 ` Laurent Pinchart
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=46250034.7000202@billgatliff.com \
--to=bgat@billgatliff.com \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=laurent.pinchart@technotrade.biz \
/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).