From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2719 invoked by alias); 29 May 2006 14:32:48 -0000 Received: (qmail 2593 invoked by uid 22791); 29 May 2006 14:32:46 -0000 X-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,TW_DW,TW_JF,TW_WM X-Spam-Check-By: sourceware.org Received: from canuck.infradead.org (HELO canuck.infradead.org) (205.233.218.70) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 29 May 2006 14:32:42 +0000 Received: from pmac.infradead.org ([81.187.2.168]) by canuck.infradead.org with esmtpsa (Exim 4.62 #1 (Red Hat Linux)) id 1FkinL-0006DI-EP; Mon, 29 May 2006 10:32:36 -0400 Subject: Re: JFFS2 on eCos From: David Woodhouse To: Gary Thomas Cc: ecos-devel@sources.redhat.com, Chi Xiaobo In-Reply-To: <1148648488.28878.43.camel@pmac.infradead.org> References: <1148599617.14160.30.camel@shinybook.infradead.org> <1148637331.20237.15.camel@hermes> <1148648488.28878.43.camel@pmac.infradead.org> Content-Type: text/plain Date: Mon, 29 May 2006 14:32:00 -0000 Message-Id: <1148913152.11358.46.camel@pmac.infradead.org> Mime-Version: 1.0 X-Mailer: Evolution 2.6.1 (2.6.1-1.fc5.2.dwmw2.1) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by canuck.infradead.org See http://www.infradead.org/rpr.html Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2006-05/txt/msg00030.txt.bz2 On Fri, 2006-05-26 at 14:01 +0100, David Woodhouse wrote: > How you do this technically is ultimately up to you. What I'd probably > suggest is that we should keep the eCos version on git.infradead.org, so > it is immediately to hand and you can quite reasonably expect people to > keep it working. With a little bit of git hacking, we should be able to > set up a git tree which contains just the OS-independent files, and > which inherits changes automatically from the main mtd-2.6.git tree. > Then we can do a git tree for the eCos version which merges from that as > and when appropriate. I've created git://git.infradead.org/~dwmw2/jffs2-ecos-core.git which contains just the JFFS2 files, moved into a 'src/' directory. It preserves the full revision history of those files from the kernel, and it's automatically updated from the kernel tree every night. It's browsable at http://git.infradead.org/?p=users/dwmw2/jffs2-ecos-core.git The script which does it, if you're interested, is at http://david.woodhou.se/extract-jffs2-git.sh -- we can redo the whole thing with a different set of $JFFS2FILES if you want. I've also created another tree which derives from the above, and added the eCos-specific files to it. That one is 'jffs2-ecos.git' in the same directory. The idea is that you can merge changes (with 'git pull') from the 'jffs2-ecos-core' tree into the working 'jffs2-ecos' tree. I haven't based the jffs2-ecos tree on the _current_ state of the exported jffs2-ecos-core; it's based on a version from November last year, which corresponds to the Andrew's last update to the eCos code in my tree -- this means that we have some expectation that it might actually build and work in eCos. It's probably work making sure that _does_ actually work before starting to pull in further changes from the upstream JFFS2 codebase. You might also want to pull the upstream changes in incrementally -- perhaps starting with commit #43220493be8f4c6b99508e78064fa557b005577c, which includes eraseblock summary support but not yet all the other changes I've made recently. Alternatively, you might prefer just to do it all in one, so that we can make changes to the upstream JFFS2 tree to make life easier. -- dwmw2