From: Gary Thomas <gary@mlbassoc.com>
To: Yuan Yu <yuany@marvell.com>
Cc: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Does eCos 1.3.1 TCP/IP stack block interrupt
Date: Mon, 25 Jul 2005 15:57:00 -0000 [thread overview]
Message-ID: <1122307006.27647.21.camel@hermes> (raw)
In-Reply-To: <D8CE9CFA707C894180BAC8CDD154F846C9047D@msiexch01.marvell.com>
On Mon, 2005-07-25 at 08:50 -0700, Yuan Yu wrote:
> Hello,
>
> Would anyone please help me on a question with eCos TCP/IP stack? We
> are using eCos 1.3.1 net. It seems the TCP/IP stack blocks interrupt
> for extremely long periods, and potentially causes interrupt loss. Can
> anyone confirm it and what is the work around?
This was definitely true. The only workaround is to move to the
newer code (1.3.1 is 5 years old!) as the changes were very large
to get this working better.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
prev parent reply other threads:[~2005-07-25 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-25 15:50 Yuan Yu
2005-07-25 15:57 ` Gary Thomas [this message]
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=1122307006.27647.21.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=yuany@marvell.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).