thanks Heiko! That seems like half of the work :) > - we should define a struct, which contains the 3 values > offset, size, destination, so we can create a "nand_load_list" > which can contain n entries, that could be processed in > a while loop ... so no need for the CONFIG_SYS_BOOT_LINUX > define ;-)
I would also add some kind of CRC to check the integrity of the image? Another question is if we not just use the uImage format provided by mkImage. This IMHO should include all this (except the offset) but then we have to read the first NAND-page (or what ever medium) to get these values which presumably means a significant slow-down. But then we can update the image without updating u-boot what i would consider important for non-dev devices. Regards Simon _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
