From owner-freebsd-mips@FreeBSD.ORG Wed May 23 19:50:04 2007 Return-Path: X-Original-To: freebsd-mips@FreeBSD.org Delivered-To: freebsd-mips@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8003C16A468 for ; Wed, 23 May 2007 19:50:04 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from out1.smtp.messagingengine.com (out1.smtp.messagingengine.com [66.111.4.25]) by mx1.freebsd.org (Postfix) with ESMTP id 57FC913C4B8 for ; Wed, 23 May 2007 19:50:04 +0000 (UTC) (envelope-from bms@incunabulum.net) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.messagingengine.com (Postfix) with ESMTP id E2F0B21F19C for ; Wed, 23 May 2007 15:50:03 -0400 (EDT) Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 23 May 2007 15:50:03 -0400 X-Sasl-enc: oLrLn3d/iPI79NebxpBJ2AtyVJJaG9e+ci8iFoAlkFjg 1179949803 Received: from [192.168.123.18] (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTP id 3D773BB14 for ; Wed, 23 May 2007 15:50:03 -0400 (EDT) Message-ID: <46549AE9.9040505@incunabulum.net> Date: Wed, 23 May 2007 20:50:01 +0100 From: "Bruce M. Simpson" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: freebsd-mips@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Anyone porting YAFFS2? X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 May 2007 19:50:04 -0000 Has anyone out there considered porting YAFFS2 to FreeBSD? Looking at the design notes it sounds fairly portable, more so than JFFS2: http://www.aleph1.co.uk/taxonomy/term/31/ This could be a good test case for flash support as it seems that a NEWBUS interface could be implemented for flash controllers, which YAFFS2 could then use. I'm not sure how GEOM would fit into this picture. The file system glue strikes me as a minimal amount of work compared to the rest involved in supporting this. Whilst the code is available under GPL, the author(s) state that they are 'open to arrangements'; I'm not sure what this implies, the licensing information on their site suggests this is about negotiating commercial licenses with them. It would seem acceptable to me that such code could potentially be imported under src/sys/contrib, however, this leaves the question of what we do about firmware images which incorporate such a YAFFS2 build. regards, BMS