This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
RE: FW: Ethernet init problem
- From: "Daniel Lidsten" <Daniel dot Lidsten at combitechsystems dot com>
- To: "Jonathan Larmour" <jifl at eCosCentric dot com>
- Cc: "Andrew Lunn" <andrew dot lunn at ascom dot ch>, "eCos Disuss" <ecos-discuss at sources dot redhat dot com>
- Date: Fri, 7 Feb 2003 10:21:21 +0100
- Subject: RE: [ECOS] FW: Ethernet init problem
Hi again,
> But another probably more promising line of attack is that
> "Init device
> 'quicc_eth'" doesn't necessarily mean your eth device itself
> was included.
> That init comes from the NETDEVTAB, but the eth0 instance is defined
> separately. Check if your program image includes quicc_eth0_sc.
I dont really follow you about the above where you say that eth0
instance is defined seperately. And yes, i have quicc_eth0_sc in my
mapfile (in extras.o) .In ConfigTool the scc2 interface name is set to
eth0 but in if_quicc.c the name of the driver was set to quicc_eth,
which the init sequnce also said with "init device: quicc_eth". However,
i changed the name in if_quicc.c to eth0 but without any result.
It feels like i dont have any connection between the network stack and
my driver. I built the ping_test to see if i maybe got into any driver
functions like quicc_eth_send, but i didnt.
I also tried to send data on the loopback interface (127.0.01) with the
ping_test but that didnt work out eighter, i got the errors:
PING server 127.0.0.1
Net malloc[16] = 0x000952b0
sendto: No buffer space available
Net malloc[16] = 0x000952b0
sendto: No buffer space available
...and so on
Any ideas?
Regards, Daniel
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss