linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Subodh Nijsure <subodh@best.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: request_irq in a module casues kernel crash
Date: Thu, 22 Mar 2001 23:01:43 -0700	[thread overview]
Message-ID: <20010322230143.G26659@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <200103230550.VAA03749@shell9.ba.best.com>; from subodh@best.com on Thu, Mar 22, 2001 at 09:50:11PM -0800


Try request_8xxirq, not request_irq.  The 8xx has its own name for
request_irq.

} I am trying to write a module where I am trying to register an interrupt
} handler using request_irq() sample code for which appears below, when
} I try to load this module, I am getting kernel panic. Anybody knows reason
} why?
} I have compiled the kernel with  CONFIG_MODULES=y CONFIG_MODVERSIONS=y
} CONFIG_KMOD=y
}
} I am using  2.4.2-pre3 on a 860 platform.
}
}
} void handler(int irq, void *dev_id, struct pt_regs * regs)
} {
}     printk("Interrupt handler invoked for irq %d \n",irq);
} }
}
} /* load the module */
} int init_module(void)
} {
}     int result;
}     result = request_irq (SIU_IRQ7, my_handler,SA_INTERRUPT,
} 		"cxeHandler",NULL);
}     if ( result )
}         printk("Interrupt not assigned");
}     else
}         printk("Interrupt  assigned");
}     return 0;
} }
}
} /* remove the module */
} void cleanup_module(void)
} {
}     return;
} }
}
} /Subodh Nijsure
}

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

  reply	other threads:[~2001-03-23  6:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-23  5:50 request_irq in a module casues kernel crash Subodh Nijsure
2001-03-23  6:01 ` Cort Dougan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-12  6:47 brijesh.chodavadiya

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=20010322230143.G26659@ftsoj.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=subodh@best.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;
as well as URLs for NNTP newsgroup(s).