This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Question about eth_drv_int_vector() in Redboot?
- From: Andrew Lunn <andrew at lunn dot ch>
- To: wang cui <iucgnaw at msn dot com>
- Cc: ecos-discuss at ecos dot sourceware dot org
- Date: Fri, 26 Jan 2007 09:43:00 +0100
- Subject: Re: [ECOS] Question about eth_drv_int_vector() in Redboot?
- References: <BAY110-F9CC5A21385921F4539271A5A20@phx.gbl>
On Fri, Jan 26, 2007 at 08:08:00AM +0000, wang cui wrote:
> When using ethernet driver in Redboot.
> Call stack:
> net_init()
> net_io_init()
> net_io_control( comm, __COMMCTL_IRQ_DISABLE )
> vector = eth_drv_int_vector()
> eth_drv_int_vector(void)
> MYDRIVER_int_vector(struct eth_drv_sc *sc);
>
> Here eth_drv_int_vector() need MYDRIVER_int_vector() to return its
> interrupt vector, but on my target, this ethernet device does not use any
> interrupt resource.
>
> How to return the vector? Presently, I return 0, and it works.
> Since 0 is a valid vector used by other driver, I suspect it is not good.
Redboot does not use interrupts, so it is not really a problem at the
moment.
If you want to use full eCos on your target then it becomes a
problem. eCos assumes the ethernet is interrupt driven so i think you
will then have more problems.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss