Re: [ECOS] cyg_interrupt_disable/enable question

[Nick Garnett <nickg at ecoscentric dot com>]

Gary Thomas <gthomas@ecoscentric.com> writes:

> On Sat, 2002-09-21 at 12:03, andy.tenka@delphiauto.com wrote:
> > 
> > 
> > One followup question:
> > 
> > Does cyg_disable_interrupt also mask the scheduler interrupt (ie, disables the
> > scheduler)?
> > Thanks.
> > 
> 
> I also forgot to mention before - don't use "cyg_disable_interrupts()",
> but rather HAL_DISABLE_INTERRUPTS().  The macros are designed to be 
> portable and will be present, no matter the platform.  The functions
> like "cyg_disable_interrupts()" are used by some platforms to perform
> the operation, but are not guaranteed to exist [they aren't part of
> the HAL API].  Use the HAL_xxx macros whenever possible.
> 

I would say quite the reverse. Always use the kernel interface: either
cyg_disable_interrupts(), cyg_drv_isr_lock(), or
Cyg_Interrupt::disable_interrupts() rather that use the HAL API directly. The
kernel interface has added semantics, and works in SMP systems where
the HAL interface does not.

Or did you mean functions like cyg_hal_disable_interrupts() that some
HALs use to implement HAL_DISABLE_INTERRUPTS() ?

-- 
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss