View Issue Details

IDProjectCategoryView StatusLast Update
0002307UBootNAND-FMDpublic2014-07-18 08:39
ReporterKeller Assigned To 
Status resolvedResolutionfixed 
Product Versionfsvybrid-V2.0 
Target Versionfsvybrid-V2.1Fixed in Versionfsvybrid-V2.1 
Summary0002307: Don't reduce NAND size by skip amount
DescriptionTo allow handling the NBoot region with a different ECC strategy, we can split the NAND MTD device in two virtual devices. One for the first part of the device (i.e. NBoot) and one for the remaining part. The first device simply has the size of NBoot, and the second device has a region of NBoot size that is skipped at the beginning of the device.

If the NAND size of this second device is reduced about the skip size, the last MTD partition (usually TargetFS) will get too small. This is not wanted. On the other hand if it is not reduced, we will count the NBoot region twice, once in each virtual device. However this region is only two blocks in size, i.e. 256K at max, and the NAND size in U-Boot is reported in MB, so it will not change the visible size at start-up. So counting slightly too much is better than wasting two blocks at the end of the device.
Forum Link


There are no notes attached to this issue.