From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 459 invoked by alias); 17 Jun 2012 09:12:32 -0000 Received: (qmail 450 invoked by uid 22791); 17 Jun 2012 09:12:31 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from tetra.codeconfidence.com (HELO tetra.codeconfidence.com) (94.229.66.225) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 17 Jun 2012 09:12:14 +0000 Received: from cog.dallaway.org.uk (cpc1-cmbg10-0-0-cust34.5-4.cable.virginmedia.com [81.102.132.35]) by tetra.codeconfidence.com (Postfix) with ESMTP id C1912234C54D; Sun, 17 Jun 2012 10:12:12 +0100 (BST) Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id q5H9CCgn016502; Sun, 17 Jun 2012 10:12:12 +0100 Message-ID: <4FDD9F6C.7030905@dallaway.org.uk> Date: Sun, 17 Jun 2012 09:12:00 -0000 From: John Dallaway User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120606 Thunderbird/10.0.5 MIME-Version: 1.0 To: Elad Yosef CC: eCos Discussion References: <4FD8B62E.6080005@kuantic.com> <4FD9F74E.7090104@kuantic.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-discuss-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: ecos-discuss-owner@ecos.sourceware.org Subject: [ECOS] Re: pbuf_alloc failures with LwIP X-SW-Source: 2012-06/txt/msg00006.txt.bz2 Hi Elad On 17/06/12 07:28, Elad Yosef wrote: > I'm using multiple threads in my application. > The SYS_ARCH_PROTECT is not enabled at all. > How do I enable it? > Is it enabled in the current CVS version? > Does the current LwIP in CVS is compatible with ecos-3.0? In yes I > would consider upgrading LwIP package only. You should be able to use lwIP 1.3.2 from eCos CVS with your eCos 3.0 release repository just by copying packages/io/eth/current/ and packages/net/lwip_tcpip/current/ into your eCos 3.0 repository. Any _new_ eCos configurations will then use the "current" versions of these packages rather than the "v3_0" versions. Any _previous_ eCos configurations will continue to use the "v3_0" packages. I hope this helps... John Dallaway eCos maintainer http://www.dallaway.org.uk/john -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss