From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27513 invoked by alias); 3 Apr 2008 11:14:56 -0000 Received: (qmail 27500 invoked by uid 22791); 3 Apr 2008 11:14:55 -0000 X-Spam-Check-By: sourceware.org Received: from mail.logix-tt.com (HELO mail.logix-tt.com) (212.211.145.186) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 03 Apr 2008 11:14:32 +0000 Received: from kingfisher.intern.logix-tt.com (84-72-190-27.dclient.hispeed.ch [84.72.190.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id F379A65C63; Thu, 3 Apr 2008 13:16:07 +0200 (CEST) Received: from kingfisher.sec.intern.logix-tt.com (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 3CD2E1D41A7; Thu, 3 Apr 2008 13:14:28 +0200 (CEST) Date: Thu, 03 Apr 2008 11:24:00 -0000 From: Markus Schaber To: ecos-discuss@ecos.sourceware.org Message-ID: <20080403131427.408359d1@kingfisher.sec.intern.logix-tt.com> In-Reply-To: <47F25AC3.1080002@mlbassoc.com> References: <20080328145148.71447eed@kingfisher.sec.intern.logix-tt.com> <20080401131413.50ebd7ee@kingfisher.sec.intern.logix-tt.com> <20080401132223.00fdfb58@kingfisher.sec.intern.logix-tt.com> <20080401112949.GB9320@lunn.ch> <20080401173918.7bc28713@kingfisher.sec.intern.logix-tt.com> <47F25AC3.1080002@mlbassoc.com> X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.9; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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: Re: [ECOS] Porting a new flash driver X-SW-Source: 2008-04/txt/msg00040.txt.bz2 Hi, Gary, Gary Thomas wrote: > Markus Schaber wrote: > > Andrew Lunn wrote: > > > >>> Ugly, because it looks like the flash driver interface consists of some > >>> static functions, so it will be impossible to support different flashes > >>> concurrently. Luckily, we'll only need a single flash unit at the > >>> moment. > >> Take a look at the flash_v2 branch. We hope that in the next few > >> months to merge this into the trunk. > > > > That sounds interesting, I'll have a look at it. But I'm afraid that, > > for now, I'll go the short path. > > Albeit more complex, using the flash_v2 branch is probably your > only choice if you want to run JFFS2 on NAND. There's quite a lot > of work involved in making this functional (hence why it's not already > in the tree!). In particular, the JFFS2 code will need to be updated > and there are many NAND specific functions which it expects to be > available which the mainline (flash_v1) does not support. It seems that the flash_v2 branch was forked 2003, so there are 5 years of differences between the branch and the trunk. So I have to step deeply into the eCos internas to figure out and merge the needed changes, it seems. Regards, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in Europe! www.ffii.org www.nosoftwarepatents.org -- Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss