This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: eth0 entry in NETDEVTBL


I just posted a question about that yesterday.

See the "SIOCSIFADDR: Device not configured" topic.

Essentially I was told to put "-library=libextras.a myfile.c" in the
"compile" line of the CDL.  This fixed the problem.

> -----Original Message-----
> From: ecos-discuss-owner@sources.redhat.com 
> [mailto:ecos-discuss-owner@sources.redhat.com] On Behalf Of 
> Sunil Mohan Savanur
> Sent: Friday, October 12, 2001 8:10 AM
> To: eCos discussion
> Subject: [ECOS] eth0 entry in NETDEVTBL
> 
> 
> Hello,
> 
> I am not developing any special network driver for my 
> synthetic target linux.
> I am planning to use existing driver that is
> "packages/io/eth/current/src/net/eth_drv.c"
> I have added CYGPKG_NET and CYGPKG_NET_ETH_DRIVERS. Then built
> eCos.
> 
> Still in my application I am getting socket/bind error ?
> 
> What is needed to make "eth0" interface active ?
> 
> Is it required to populate the "eth0" entry in NETDEVTBL as a part of
> initialization ?
> 
> Looks like eth_drv_net("eth0") call does not find any valid 
> entry in NETDEVTBL
> !!
> 
> Please guide me.
> 
> Thanks & regards
> Sunil Savanur
> 
> 
> 


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]