From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marek.vasut@gmail.com>
Date: Sun, 13 May 2012 19:09:08 +0200
Subject: [U-Boot] UBI: volume auto-resize
In-Reply-To: <7C1B161B-1EEE-47C2-826D-201DF5C70588@borea.si>
References: <7C1B161B-1EEE-47C2-826D-201DF5C70588@borea.si>
Message-ID: <201205131909.09021.marek.vasut@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Matevz Langus,

> Hi,
> 
> I found an interesting situation where I can not decide whether it is a bug
> or functionality that should not be included at all.
> 
> If I generate UBI image consisting of 3 Volumes to NAND flash on my board,
> U-boot  does not attach UBI to MTD. This happens only if UBI contains a
> volume that has auto-resize flag set. U-boot tries to resize it but fails.
> 
> Just started fixing it, but I have a question. Is it desirable that U-boot
> changes something in the FS? Would it not be better if U-boot would just
> read things out (that is all I want, to get uImage and dtb file) and leave
> the rest to Linux. (Linux handles the procedure without any issues).
> 
> Any opinion welcome.
> 
> Creating 1 MTD partitions on "nand0":
> 0x000000200000-0x000008000000 : "mtd=2"
> Bad block table found at page 65472, version 0x01
> Bad block table found at page 65408, version 0x01
> nand_read_bbt: Bad block at 0x0000011a0000
> UBI: attaching mtd1 to ubi0
> UBI: physical eraseblock size:   131072 bytes (128 KiB)
> UBI: logical eraseblock size:    129024 bytes
> UBI: smallest flash I/O unit:    2048
> UBI: sub-page size:              512

Is the subpage size here correct? I know at least about one driver that might 
misreport it under certain conditions.

Best regards,
Marek Vasut