On 25.04.2013 14:38, Marek Vasut wrote: >>> Right, this is also correct. Anyway, BOOT_FROM is used to get the offset >>> inside the storage, and only to be as much flexible as possible, each >>> storage has defined its own offset. However, Freescale uses the same >>> offset (0x400) for most storages (NAND, SD..) and another one for NOR or >>> OneNAND (0x1000). Maybe it is easier to have only this two cases. >> >> Yes, I would prefer that. >> >> And being at it, why don't we add the offset to the resulting image as >> well? This would make programming the images to the destination (SD, >> NAND, MMC etc) easier. We would not have to care for the correct offset >> then (which is more error prone). And it is necessary btw, to have this >> offset added, when using the FSL kobs-ng tool to program the image to >> NAND flash. > > This would interfere with MBR on SD cards, the offset is there for a reason > ;-)
Yes, makes sense. But only for SD cards. On other mediums (e.g. SPI NOR, NAND) this padded image would be easier (less error prone) to handle. Thanks, Stefan _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
