Dear "Cote, Sylvain",
I re-added the mailing list, as others might be interested, too.
Also, please don't top post / full quore. Please read http://www.netmeister.org/news/learn2quote.html
In message 579B119545DAEF4689C8FBEEFEC5793F01D4FDF6E83B@ATLMBX.verint.corp.verintsystems.com you wrote:
The NAND layout you mean is:
SPL (in first nand block) u-boot config (N blocks depending on spare place allocated) nand u-boot
This is one of the options - but you can chose those as you like.
Can we do or is it a good idea to do:
SPL Nand u-boot u-boot config
You can of course do that as well.
Maybe in the second layout there are chances to overwrite config in case that at some moment new bad block occurs (after few u-boot update).
In each and evary configuration you should leave some room for spare blocks in case you need them.
Even better, don't use such a fixed block mapping, but use UBI instead. [Hoewver, booting from a UBI volume might be a challenge if your NAND controller reads only a small initial block like 4 KiB...]
Please keep in mind that you must not use NAND like you used to use hard disk drives. Please see for example http://download.micron.com/pdf/technotes/nand/tn2917.pdf - this explains nicely why you want UBI.
Best regards,
Wolfgang Denk