On 08/18/2011 11:25 AM, Scott Wood wrote: > The NOP restrictions should be documented in the code itself, not just > in the git changelog. Maybe print it to the console when this hack is > used, along with the NOP value read from the ID. If it's less than 4 > for 4K or 8 for 8K, also print a message saying not to use jffs2 (does > yaffs2 do similar things?). If it's less than 2 for 4K or 4 for 8K, the > probe should fail.
We should also warn the user about the need to prepare the NAND chip by copying the bad block markers to the OOB of the new layout. -Scott _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
