[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-gcc-list] interrupts
From: |
Jamie Morken |
Subject: |
Re: [avr-gcc-list] interrupts |
Date: |
Thu, 17 Mar 2005 14:25:09 -0800 |
Hi,
----- Original Message -----
From: "E. Weddington" <address@hidden>
Date: Thursday, March 17, 2005 2:13 pm
Subject: Re: [avr-gcc-list] interrupts
> It depends on how you have your ISRs defined. Are you using
> SIGNAL() or
> INTERRUPT()?
I an using SIGNAL() up until now
The explanation for SIGNAL() in the avr-libc manual is a bit light, it makes it
sound like you don't need to enable sei(); to run SIGNALS:
SIGNAL()
"Introduces an interrupt handler function that runs with global interrupts
initially disabled."
INTERRUPT()
"Introduces an interrupt handler function that runs with global interrupts
initially enabled. This allows interrupt handlers to be interrupted."
--so you can interrupt an interrupt with this one?
So if I declare one ISR as INTERRUPT and the rest as SIGNAL, then the INTERRUPT
can be interrupted by the SIGNAL's? :) wow..
cheers,
Jamie
- [avr-gcc-list] interrupts, Jamie Morken, 2005/03/17
- Re: [avr-gcc-list] interrupts, Christopher X. Candreva, 2005/03/17
- Re: [avr-gcc-list] interrupts, E. Weddington, 2005/03/17
- Re: [avr-gcc-list] interrupts, Ben L. Titzer, 2005/03/17
- Re: [avr-gcc-list] interrupts, Ben L. Titzer, 2005/03/17
- RE: [avr-gcc-list] interrupts, Larry Barello, 2005/03/17