From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-ew0-f223.google.com ([209.85.219.223]) by bombadil.infradead.org with esmtp (Exim 4.69 #1 (Red Hat Linux)) id 1NMr6P-0000qX-0q for linux-mtd@lists.infradead.org; Mon, 21 Dec 2009 22:51:49 +0000 Received: by ewy23 with SMTP id 23so5001700ewy.4 for ; Mon, 21 Dec 2009 14:51:43 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <4B2FA658.6010407@wyplay.com> Date: Mon, 21 Dec 2009 17:51:43 -0500 Message-ID: Subject: Re: UBI - exclude bootloader blocks from wear levelling From: twebb To: Darwin Rambo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "linux-mtd@lists.infradead.org" , Lauren Del Giudice List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , > Wear levelling is done across a "ubi device" (not the whole nand device) = which is associated with a mtd partition. Your bootloader and kernel mtd pa= rtitions will not be wear levelled, only your ubi file system partitions. i= .e. ubi doesn't know about non-ubi mtd partitions. > > I think that's the gist of it. > > Darwin > That's my understanding also. Could you maybe clarify another point? If I wanted to exclude some blocks that contain boot code (like Lauren's question), and the leftover space on the NAND device was ultimately going to be used for four different volumes, does it make the most sense to... a) define one MTD partition that includes all NAND space (except the blocks reserved for boot code); and then define one UBI device that attaches to the MTD device and includes the four volumes (ubi0_0, ubi0_1, ubi0_2, ubi0_3) OR b) define four MTD partitions that include all NAND space (except the blocks reserved for boot code); and then define four UBI devices that attach to the MTD devices and each UBI device has one volume associated with it (ubi0_0, ubi1_0, ubi2_0, ubi3_0)? Thanks, twebb