On Tue, Jul 08, 2008 at 11:05:10AM -0500, Scott Wood wrote:
Therefore, I still believe that such a feature is useful and should be merged into u-boot. If there are problems with my particular implementation, I'm happy to address them.
Can you base it off of the testing branch of the u-boot-nand-flash repo?
Will do. Probably by tomorrow.
I also have another patchset for what I call 'dynpart' support, i.e. the dynamic calculation of a unit-specific partition table that ensures the net size of partitions are as per spec, no matter how many of the factory default blocks are located where. So it would even support NAND devices with a worse spec than the ones that we were using.
Interesting... Would such a patch eliminate the need for this one, by making the environment a dynamic partition? Is there any (plan for) Linux support?
no, the dynamic partition table is calculated once and then stored in the environment. Therefore, the environment has to be either stored outside the NAND flash, or located by the OOB marker. Therefore, the dynpart patch bases on top of the dynenv patch.
Linux has no need to support it, since it gets the device-unique partition table passed by the standard commandline mtdparts mechanism.