Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Steve Papacharalambous <stevep@lineo.com>
Cc: linux-mips@oss.sgi.com
Subject: Re: Interrupts in modules
Date: Sun, 22 Jul 2001 11:28:37 -0700	[thread overview]
Message-ID: <20010722112837.A22440@lucon.org> (raw)
In-Reply-To: <3B59FC0D.6CAD443C@lineo.com>; from stevep@lineo.com on Sat, Jul 21, 2001 at 11:02:53PM +0100

On Sat, Jul 21, 2001 at 11:02:53PM +0100, Steve Papacharalambous wrote:
> Hi All,
> 
> Are there any limitations or precautions needed with interrupt handlers
> in loadable modules?
> 
> The reason for asking is that I have an interrupt handler which works
> fine when compiled into the kernel, but causes the kernel to crash when
> it is a loadable module,

There are some gas bugs which may generate the bad binary code. It
happened to me with the tulip driver. The current Linux binutils
should be ok.


H.J.

      parent reply	other threads:[~2001-07-22 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-21 22:02 Interrupts in modules Steve Papacharalambous
2001-07-22  1:17 ` Keith Owens
2001-07-22 18:28 ` H . J . Lu [this message]

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=20010722112837.A22440@lucon.org \
    --to=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=stevep@lineo.com \
    /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