This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: __NETDEVTAB__ length is zero
- To: Gary Thomas <gthomas at redhat dot com>
- Subject: Re: [ECOS] __NETDEVTAB__ length is zero
- From: Chandra Sekhar G <chandra at danlawinc dot com>
- Date: Sat, 10 Nov 2001 19:11:18 +0530
- Cc: chandrag at danlawinc dot com, eCos Discussion <ecos-discuss at sources dot redhat dot com>
- Organization: DTIL
- References: <3BEAA8C5.957F39AB@danlawinc.com> <1005435392.9795.55.camel@station91>
- Reply-to: chandrag at danlawinc dot com
Gary Thomas wrote:
> On Fri, 2001-11-09 at 00:46, Chandra Sekhar G wrote:
> > Hi,
> >
> > We are using cs9800 controller on a custom designed board. I am
> > able to run the TCP/IP loop back tests on this board. In the present
> > configuration of eCos, when I see the object dump of a test program (not
> > a loop back program), the two global variables __NETDEVTAB__ and
> > __NETDEVTAB_END__ are having a same address. This means, there are no
> > entries in the network device table. I think, I am missing something
> > during the configuration of eCos. Can anybody give me a clue? I did
> > not configured any of the other devices. I am using latest sources of
> > eCos.
>
> You'll need to provide a network driver structure for your controller.
> Look at the driver provided for the Cirrus Logic EDB7xxx family of
> processors for an example.
> .../devs/eth/arm/edb7xxx/
Hi,
The controller we are using is cs8900. We are directly using the driver
code of ..../dev/eth/arm/edb7xx/, after putting in a proper directory
structure and a few modifications to the addresses. All the related cdl
files are also identical. Still the problem persists.
regards,
chandra