From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 619 invoked by alias); 16 May 2009 09:50:21 -0000 Received: (qmail 608 invoked by uid 22791); 16 May 2009 09:50:20 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from rubicon.hasler.ascom.ch (HELO rubicon.hasler.ascom.ch) (139.79.129.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 16 May 2009 09:50:14 +0000 Received: from eiger.ma.tech.ascom.ch (eiger.ma.tech.ascom.ch [139.79.100.1]) by rubicon.hasler.ascom.ch (8.14.1/8.14.1) with ESMTP id n4G9o83w009279; Sat, 16 May 2009 11:50:08 +0200 (MEST) Received: from [139.79.100.143] (helo=donkey.ma.tech.ascom.ch) by eiger.ma.tech.ascom.ch with esmtp (Exim 3.16 #1) id 1M5GWs-0006tJ-00; Sat, 16 May 2009 11:50:06 +0200 Received: from lunn by donkey.ma.tech.ascom.ch with local (Exim 4.69) (envelope-from ) id 1M5GWu-0004Nf-2x; Sat, 16 May 2009 11:50:08 +0200 Date: Sat, 16 May 2009 09:50:00 -0000 From: Andrew Lunn To: Simon Kallweit Cc: Rutger Hofman , Ross Younger , ecos-maintainers@ecos.sourceware.org, Sergei Gavrikov , Melanie Rieback , Paul Beskeen Subject: Re: NAND & YAFFS Message-ID: <20090516095007.GC31991@ma.tech.ascom.ch> References: <4A0AD212.60208@ecoscentric.com> <4A0C6674.5030006@cs.vu.nl> <20090515095150.GH17679@ma.tech.ascom.ch> <4A0D4189.6040109@intefo.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A0D4189.6040109@intefo.ch> User-Agent: Mutt/1.5.18 (2008-05-17) X-IsSubscribed: yes Mailing-List: contact ecos-maintainers-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@ecos.sourceware.org X-SW-Source: 2009-05/txt/msg00018.txt.bz2 On Fri, May 15, 2009 at 12:18:49PM +0200, Simon Kallweit wrote: > Andrew Lunn wrote: >> Hi Folks [...] >> There is a possibility of it happening again soon >> as well. eCosCentric have a more modern lwIP port in there tree than >> the current in anoncvs. I understand they have optimized it for small >> platform and made it more stable. There is the current effort going on >> to update the anoncvs lwip code. When this reaches maturity, which >> looks like will happen soon, are eCosCentric going to pull out there >> trump card again and contribute there lwip port? > > Well well, I almost saw that coming :/ Would eCosCentric like to make a comment regarding this subject? Andrew