From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp42.singnet.com.sg ([165.21.103.146]) by canuck.infradead.org with esmtp (Exim 4.54 #1 (Red Hat Linux)) id 1FIbRM-0001Wm-TY for linux-mtd@lists.infradead.org; Sun, 12 Mar 2006 20:01:45 -0500 Message-ID: <4414BE02.3080300@singnet.com.sg> Date: Mon, 13 Mar 2006 08:34:10 +0800 From: Terence Soh MIME-Version: 1.0 To: Russ Dill , Josh Boyer References: <44079DE4.3070804@singnet.com.sg> <625fc13d0603100506k31e3da28kd51f65712447165b@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-mtd@lists.infradead.org Subject: Re: Cramfs on NAND List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hi, >>Yes, it's still true. CRAMFS expects it's data to be contiguous so >>unless you have something similar to a flash translation layer that >>hides the bad blocks, insanity will ensue. FTL will not work for me because of the licensing issues :(. >>Could you use a read-only JFFS2 partition? Besides the read-only characteristic, I'm also looking at fast mount time. I guess I should take a look at YAFFS. Question: Does a read-only JFFS2/YAFFS partition means that there will not be any wear-levelling performed? > > > The other solution is to use an ftl ontop of the flash, and then put a > cramfs on that. Of course, that depends on you living somewhere where > algorithms are not restricted to those with the license to use them. > (iirc) > Bye and thanks for your time, Terence.