This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Interrupt unmask before complete cs8900a interrupt configuration.
On Wed, 2006-01-11 at 13:05 +0100, Andrew Lunn wrote:
> On Wed, Jan 11, 2006 at 11:48:36AM +0100, Jaws wrote:
> > If redboot stops the ethernet chip when lauch the application,
> > I don't understand why before the cs8900a_start, when unmask the interrupt,
> > it is active! The redboot is the current CVS version.
>
> The current code to stop the driver is:
>
> static void
> cs8900a_stop(struct eth_drv_sc *sc)
> {
> cs8900a_priv_data_t *cpd = (cs8900a_priv_data_t *)sc->driver_private;
> cyg_addrword_t base = cpd->base;
>
> put_reg(base, PP_LineCTL, 0);
> }
>
> Is this enough to really stop the chip?
It's enough to stop the chip from "talking".
I think Jaws has some other problem though - this chip has been used
on a wide variety of platforms and there has never been a problem
with interrupts before. Perhaps the IRQ being used is shared with
some other piece of hardware which is asserting interrupts?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss