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 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
