public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Hugo 'NOx' Tyson <hmt@cygnus.co.ukx>
To: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS]TCP/IP problem
Date: Mon, 04 Sep 2000 04:15:00 -0000	[thread overview]
Message-ID: <pt3djg8l5x.fsf@masala.cygnus.co.uk> (raw)
In-Reply-To: <001d01c01611$f8f78500$bd2da8c0@lqx.star.com.cn>


"lqx" <liqx@term.star.com.cn> writes:
>  I have got ecos running on our board using the CL_PS7500FE ARM =
> processor. I have included  DM9008  ethernet chip and use the tcp/ip =
> stack version 1_0b1 that I downloaded from the =
> URL--sourceware.cygnus.com  .The chip really works.But when I ping the =
> ecos with a packet more than 1500 bytes,the ecos never send the packet =
> back.Why?Is there any bug in the tcp/ip stack?for when I debugged  the =
> net device driver, I found the driver received the packet correctly =
> Anyone can help me?

I don't remember the details, but I remember encountering the same problem,
and I think that this change was the fix for it:

(in net/tcpip/VERSION/ChangeLog)
   2000-06-23  Hugo Tyson  <hmt@cygnus.co.uk>

        * src/ecos/support.c (cyg_net_mbuf_alloc, cyg_kmem_init): Align
        the mbuf pool to MSIZE [128] bytes.  That way dtom() works, nasty
        though it is.  That's needed for ip reassembly in ip_input.c, when
        dealing with large icmp-layer packets eg. ping -s 2000 ...

So perhaps if you update from anoncvs?

HTH,
	- Huge

  reply	other threads:[~2000-09-04  4:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-03 18:45 lqx
2000-09-04  4:15 ` Hugo 'NOx' Tyson [this message]
2001-12-26  5:26 [ECOS] TCP/IP problem Raman Sivam
2002-09-26 23:29 Marc Pignat
2002-09-27  5:08 ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pt3djg8l5x.fsf@masala.cygnus.co.uk \
    --to=hmt@cygnus.co.ukx \
    --cc=ecos-discuss@sourceware.cygnus.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).