From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22317 invoked by alias); 20 May 2009 15:25:39 -0000 Received: (qmail 22300 invoked by uid 22791); 20 May 2009 15:25:38 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 20 May 2009 15:25:34 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id B547A3B40057; Wed, 20 May 2009 16:25:32 +0100 (BST) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FpQisl1O0H3C; Wed, 20 May 2009 16:25:31 +0100 (BST) Message-ID: <4A1420E3.20808@ecoscentric.com> Date: Wed, 20 May 2009 15:25:00 -0000 From: Ross Younger User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: Gary Thomas CC: Andrew Lunn , Simon Kallweit , "ecos-devel@ecos.sourceware.org" Subject: Re: NAND review References: <4A126D59.7070404@intefo.ch> <4A12B877.9030404@ecoscentric.com> <20090519141710.GJ20046@lunn.ch> <4A1410BA.3040808@ecoscentric.com> <4A1411F0.1070805@mlbassoc.com> In-Reply-To: <4A1411F0.1070805@mlbassoc.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-05/txt/msg00059.txt.bz2 Gary Thomas wrote: > I don't know what/where you were looking to come to these conclusions :-( > Linux MTD has had the ability to use the RedBoot FIS directory for many (7+) years. At the moment, as I understand things, FIS implies io/flash, which pretty much implies NOR. I don't have any plans to implement FIS on top of NAND; people who do use NAND will generally be using a filesystem, so "obviously" the right place to put static config data is on that filesystem? (Chicken, meet egg?) Now, if we were to need to write a primary bootloader - say, if a OneNAND-based SOC came into the frame and we wanted to run RedBoot on it - then we might very well find ourselves needing something along these lines. A very very simple filesystem, combined perhaps with the ability to store a little config data and/or partition table layout, for which it might be worth considering reusing some or all of the FIS code? With that in mind, I suppose that defining a scheme for a partition table and very simple FS for NAND would be a worthwhile exercise, which could then of course be contribbed to Linux. Comments? Ross -- Embedded Software Engineer, eCosCentric Limited. Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK. Registered in England no. 4422071. www.ecoscentric.com