Re: [ECOS] Problems receiving packets on i82559

[Andrew Lunn <andrew dot lunn at ascom dot ch>]

OK. That helps. It also makes the problem field much bigger. My guess
is you are not using the eth_drv.c api correctly. Have you look at say
the lwip stack to see how its interface to eth_drv.c works? There is
also some documentation in io/eth/current/doc which you should read.

You buffer management could be broken. If you are not correctly
receiving the packets the RX ring could be filling up. Once the Rx
ring is full, the device stops receiving until you empty the ring and
kick the device. This would fit the problem you describe, particularly
if you have lots of multicast traffic on your network.

   Andrew

On Tue, Mar 11, 2003 at 04:52:37PM +0530, Nikhil R. wrote:
> Hi,
> 
> We r developing a TCP/IP stack on ecos. We r trying to integrate the same
> with the i82559 driver. We have an initialization routine where in we call
> i82559_init through the pointer in NETDEVTAB entries. Seems like the init is
> happening fine. At the end of this we r trying to send some multicast
> packets. Using tcpdump on another machine we were able to see that these
> packets are being sent out correctly.
> 
> We receive packets for sometime after the send but the problem is that we
> stop receiving any packets after a short interval of time. This cud be
> because we have just sent some packets. 
> 
> So we stopped sending out packets after initialization and instead tried to
> call eth_drv_start to try and bring the interface up. Still we were able to
> receive packets for only sometime after which it stopped.
> 
> Can u tell us the way to get over this problem?
> 
> Thanx,
> Nikhil
> 
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew dot lunn at ascom dot ch]
> Sent: Tuesday, March 11, 2003 4:39 PM
> To: Nikhil R.
> Cc: Andrew Lunn; ecos-discuss at sources dot redhat dot com
> Subject: Re: [ECOS] Problems receiving packets on i82559
> 
> 
> On Tue, Mar 11, 2003 at 04:33:22PM +0530, Nikhil R. wrote:
> > Hi Andrew,
> > 
> > Thanx for ur help. to answer some of ur questions.....
> > 
> > We have checked the MAC address. It is the same as the MAC address we get
> > when using Redboot. It is printing the MAC address correctly.
> > 
> > We r able to send packets out without calling init_all_network_interfaces.
> > But the problem is with receiving. The other thing is we dont want the
> > application to make a call to init_all_network_interfaces or any other
> > similar function. Is it possible to have the interface up continously so
> tht
> > we dont need to call any function as part of the application?
> > 
> > We called eth_drv_start at the end of our initialization procedure. As a
> > result of this we received some interrupts but this again stopped after
> > sometime.
> 
> You need to explain what you are trying to achieve in more detail. You
> seem to be doing something very strange, so we need some more
> background information to tell you if its possible to do what you want
> to do.
> 
>        Andrew
> 
> 
> DISCLAIMER:
> This message (including attachment if any) is confidential and may be privileged. Before opening attachments please check them for viruses and defects. MindTree Consulting Private Limited (MindTree) will not be responsible for any viruses or defects or any forwarded attachments emanating either from within MindTree or outside. If you have received this message by mistake please notify the sender by return  e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited.  Please note that e-mails are susceptible to change and MindTree shall not be liable for any improper, untimely or incomplete transmission.

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