From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] UBI: volume auto-resize
Date: Sun, 13 May 2012 19:09:08 +0200 [thread overview]
Message-ID: <201205131909.09021.marek.vasut@gmail.com> (raw)
In-Reply-To: <7C1B161B-1EEE-47C2-826D-201DF5C70588@borea.si>
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
next prev parent reply other threads:[~2012-05-13 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-11 22:33 [U-Boot] UBI: volume auto-resize Matevz Langus
2012-05-13 17:09 ` Marek Vasut [this message]
2012-05-13 17:45 ` Matevz Langus
2012-05-13 18:51 ` Marek Vasut
2012-05-15 10:19 ` Matevz Langus
2012-05-15 16:33 ` Marek Vasut
2012-05-15 17:26 ` Scott Wood
2012-05-15 17:59 ` Matevz Langus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201205131909.09021.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.