This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Spurious Interrupt Handling
- From: Andy Atkinson <andya at hydrix dot com>
- To: ECOS Newgroup <ecos-discuss at sources dot redhat dot com>
- Date: 22 Mar 2005 09:11:56 +1100
- Subject: [ECOS] Spurious Interrupt Handling
- Organization:
Hi All,
When a spurious interrupt is detected, where does the scheduler get
unlocked if build option CYGIMP_HAL_COMMON_INTERRUPTS_IGNORE_SPURIOUS is
defined? From my instrumentation trace it looks like it is never fully
unlocked once a spurious interrupt has occurred. Is it necessary to
modify vectors.S to handle this unlocking?
Cheers
Andy
--
=================================
Andy Atkinson
Software Engineer
Hydrix Pty Ltd.
1044A Dandenong Rd,
Carnegie, VIC, 3146,
Melbourne,
Australia
Phone : +61 3 9572 0686, Ext. 114
Fax : +61 3 9572 2686
Email : andya@hydrix.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss