From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 213-239-205-147.clients.your-server.de ([213.239.205.147] helo=debian.tglx.de) by canuck.infradead.org with esmtp (Exim 4.33 #1 (Red Hat Linux)) id 1C39ZN-0003oB-4S for linux-mtd@lists.infradead.org; Fri, 03 Sep 2004 04:37:19 -0400 From: Thomas Gleixner To: Nick Bane In-Reply-To: References: Content-Type: text/plain Message-Id: <1094200720.3681.3.camel@lap02.tec.linutronix.de> Mime-Version: 1.0 Date: Fri, 03 Sep 2004 10:38:40 +0200 Content-Transfer-Encoding: 7bit Cc: "Balloon@Balloonboard.Org" , yaffs list , "Linux-Mtd@Lists.Infradead.Org" Subject: Re: yaffs update#2 Reply-To: tglx@linutronix.de List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Thu, 2004-09-02 at 19:56, Nick Bane wrote: > Hi folks, > There are moves afoot to submit yaffs to mainstream linux. > All opinions about suitability/maturity welcome. The kernel > mtd layer and yaffs_mtdif have now harmonised so now seems > a good moment. Can we look into use the automatic placement of OOB data. Then it would be using the same mechanisms as JFFS2 and it would be easy to use YAFFS on DOC and other devices which cannot use the fixed OOB layout scheme ? tglx