From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 95BDFDDF19 for ; Fri, 21 Mar 2008 04:18:43 +1100 (EST) Message-ID: <47E29C60.10300@freescale.com> Date: Thu, 20 Mar 2008 12:18:24 -0500 From: Scott Wood MIME-Version: 1.0 To: Tehn Yit Chin Subject: Re: interrupt handlers PowerPC via GCC References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Cc: linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Tehn Yit Chin wrote: > Hi all, > > Apologies for such a basic question. I am trying to write an ISR on a > MPC551x. When I tried to use the interrupt attribute with > powerpc-eabi-gcc such as > > _attribute_((interrupt_handler)) foobarISR(void) > { > } Assuming you're talking about an interrupt handler in Linux, you don't need to do anything like that. The actual interrupt entry is assembly code. Search existing drivers for "irqreturn_t" to find examples of what an interrupt handler looks like, and "request_irq" for how to hook the handler into the interrupt. -Scott