This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: ISR occurs, but DSR does not.
- To: "Trenton D. Adams" <tadams at extremeeng dot com>
- Subject: Re: [ECOS] ISR occurs, but DSR does not.
- From: Jonathan Larmour <jlarmour at redhat dot com>
- Date: Wed, 04 Jul 2001 21:36:44 +0100
- Cc: 'eCos discussion' <ecos-discuss at sources dot redhat dot com>
- Organization: Red Hat UK Ltd.
- References: <000001c104c4$20dfe610$090110ac@TRENT>
"Trenton D. Adams" wrote:
>
> >
> > At a guess the interrupt is not being acked properly
> > causing it to loop doing the ISR because it will keep
> > regenerating the interrupt when interrupts are re-enabled.
> >
> > Also you have to return
> > CYG_ISR_HANDLED|CYG_ISR_CALL_DSR from your ISR for it
> > to call the DSR.
>
> Wouldn't this cause my CYG_TRACE to print to the screen several times?
In that case, yes it presumably isn't that then.
> I'm sure I'm clearing the interrupt properly. If I didn't clear it
> properly on the PCMCIA controller side, I would get a whole bunch of
> interrupts really quickly. Even if this happens, my DSRs are still used
> every time.
They _are_ still used? Just to be clear, from what you described before it
seems that everything just freezes when a card is inserted, right? Do you
have any idea what's happening when that happens?
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/