public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* [ECOS] Ping problem in TCP/IP
@ 2002-07-15  6:10 Khasim
  2002-07-15  6:33 ` Gary Thomas
  0 siblings, 1 reply; 2+ messages in thread
From: Khasim @ 2002-07-15  6:10 UTC (permalink / raw)
  To: ecos-discuss

Greetings

I have ported TCP/IP stack and FEC driver for MPC860 based board.
When I start The FEC driver is giving interrupts for the network packets
received.
If suppose I ping to the IP address which I have given statically.This is
not replied.
Should I used init_all_network_interfaces???

Thanks
Khasim


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [ECOS] Ping problem in TCP/IP
  2002-07-15  6:10 [ECOS] Ping problem in TCP/IP Khasim
@ 2002-07-15  6:33 ` Gary Thomas
  0 siblings, 0 replies; 2+ messages in thread
From: Gary Thomas @ 2002-07-15  6:33 UTC (permalink / raw)
  To: Khasim; +Cc: eCos Discussion

On Mon, 2002-07-15 at 06:54, Khasim wrote:
> Greetings
> 
> I have ported TCP/IP stack and FEC driver for MPC860 based board.
> When I start The FEC driver is giving interrupts for the network packets
> received.
> If suppose I ping to the IP address which I have given statically.This is
> not replied.
> Should I used init_all_network_interfaces???

This is now something like the fifteenth (15!) email you've sent to this
list, asking the same question.  This does nothing more than aggravate
those of us who are trying to use the list.  It certainly does not
expedite any replies.

What have you done to investigate this problem?
 * Have you verified that your hardware does anything?  e.g. are you 
    running RedBoot on the hardware?  Can it (RedBoot) use the network?
 * Does your device have a valid ESA (Ethernet Station Address, 
   sometimes poorly refered to as the MAC address)?
 * When you call 'init_all_network_interfaces()' (and yes, it does have 
   to be called unless you set things up 100% static using the CDL, or 
   provide equivalent code) will be to run DHCP to get an address for 
   your device. Does this do anything?  (You can see by turning on 
   DHCP_CHATTER in the DHCP code, and/or by watching the network with a 
   network monitor).
 * Have you validated any assumptions in the driver?  I know that driver    
   is a little "tied" to the A&M Viper.  For example, the way in which
   the interrupts are setup (the viper gets the FEC interrupt from SIU 
   level 1).

note: I won't be answering any followups to this, especially if you send
them directly to me.  Personal response(s) are only available if you 
want to contract for my time.


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-07-15 13:33 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-15  6:10 [ECOS] Ping problem in TCP/IP Khasim
2002-07-15  6:33 ` Gary Thomas

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).