From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8003 invoked by alias); 25 Jul 2005 15:50:40 -0000 Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Received: (qmail 7965 invoked by uid 22791); 25 Jul 2005 15:50:33 -0000 Received: from host2.marvell.com (HELO maili.marvell.com) (65.219.4.2) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Mon, 25 Jul 2005 15:50:33 +0000 Received: from MSI-MTA.marvell.com (msi-mta.marvell.com [10.68.76.91]) by maili.marvell.com (Postfix) with ESMTP id D741426C9 for ; Mon, 25 Jul 2005 08:50:31 -0700 (PDT) Received: from msiexch01.marvell.com ([10.68.76.102]) by MSI-MTA.marvell.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 25 Jul 2005 08:50:31 -0700 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 25 Jul 2005 15:50:00 -0000 Message-ID: From: "Yuan Yu" To: Subject: [ECOS] Does eCos 1.3.1 TCP/IP stack block interrupt X-SW-Source: 2005-07/txt/msg00256.txt.bz2 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? Thank you very much! Yuan -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss