This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ISR and DSR
- To: ecos-discuss at sourceware dot cygnus dot com
- Subject: Re: [ECOS] ISR and DSR
- From: Nick Garnett <nickg at cygnus dot co dot uk>
- Date: 29 Aug 2000 15:04:25 +0100
- Newsgroups: cygnus.sourceware.ecos.d
- Organization: Cygnus Solutions, a Red Hat company (Cambridge, UK)
- References: <8AE4B526B977D411841F00A0CC334020052C2E@cuz-exchange.sdesigns.net>
Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:
> Hi,
>
> Can I attach an ISR and no DSR to an interrupt? In this case what value
> does the ISR have to return?
>
> For the moment, at the end of the ISR I return CYG_ISR_HANDLED and when
> creating the interrupt I put a NULL pointer instead of a pointer to the DSR.
> But at one moment, something goes wrong in call_pending_DSRs_inner.
>
What you are doing should work. However, for safety, I would pass a
pointer to an empty DSR function rather than NULL, just in case it
gets called by accident. At the very least, that would tell you
whether the problems you are having in call_pending_DSRs_inner() is
due to the NULL DSR pointer.
--
Nick Garnett, eCos Kernel Architect
Red Hat, Cambridge, UK