changing mtd partitioning

Andy Green andy at
Fri Apr 11 08:58:40 CEST 2008

Hash: SHA1

Somebody in the thread at some point said:

|> There's truth in advertisement - the bad block table indeed only contains
|> the bad blocks :-) The partition "table" is stored in the environment, in
|> the variable mtdparts. (Yeah, ugly as it gets ...)
| What does dynpart refer to then when it says is reads from BBT. And why
| doesn't dynpart obey what is written in the env?

I think dynpart creates the custom partition list in the env, having
custom-bloated partition sizes with bad blocks accordingly.  This has
the amazing feature that partition starts on different GTA02 can be at
different offsets in the NAND.

Reeling with disgust from this (and the fact that the block devices in
Linux for this do NOT account for bad blocks, some sectors in the block
device may just not work) is a major factor from my side anyway in
trying to can NAND, U-Boot and almost entirely the bootloader
environment concept in future products.

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the openmoko-kernel mailing list