From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16597 invoked by alias); 13 May 2009 19:03:58 -0000 Received: (qmail 16459 invoked by uid 22791); 13 May 2009 19:03:56 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 13 May 2009 19:03:49 +0000 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090513190346.BLFD29481.mtaout02-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com>; Wed, 13 May 2009 20:03:46 +0100 Received: from cog.dallaway.org.uk ([86.9.207.237]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090513190346.XEPN13254.aamtaout01-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Wed, 13 May 2009 20:03:46 +0100 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 n4DJ3hdk020520; Wed, 13 May 2009 20:03:43 +0100 Message-ID: <4A0B198F.6020109@dallaway.org.uk> Date: Wed, 13 May 2009 19:03:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: Ross Younger CC: ecos-maintainers@ecos.sourceware.org, Rutger Hofman , Simon Kallweit , Sergei Gavrikov Subject: Re: NAND & YAFFS References: <4A0AD212.60208@ecoscentric.com> In-Reply-To: <4A0AD212.60208@ecoscentric.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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/msg00010.txt.bz2 Hi Ross Ross Younger wrote: > We (eCosCentric) have been working on a NAND layer for eCos and integration > with YAFFS, which we intend to contribute. Unfortunately, due to commercial > considerations - including licensing and technical discussions with Aleph > One - we have previously had to keep quiet about it. We can now talk about > this work publicly, and would like to explore how the best overall solution > for the eCos project can be pulled together. Good news! > Obviously two alternative implementations and further duplication of work is > best avoided, so we have opened a discussion with Rutger to see if there are > ways in which we can work together to try and find a common "best of breed" > technical solution. > > It seems sensible that the maintainers are aware of this discussion and have > the opportunity to provide input and direction. [ snip ] > Please let me know your thoughts. I can provide an interim documentation or > code drop if you'd like to see one. (The NAND layer is complete; YAFFS is > still being worked on, and RedBoot will be next.) Which board have you targeted initially? One of my concerns is that the NAND subsystem interfaces are appropriate for other filesystems (such as UFFS) and for a broad range of NAND devices. An interim code drop with any existing documentation would be very welcome to kick-start the discussion. John Dallaway