Andy Green wrote: > I think we can get around it for now by checking for NULL filepath name > if it's RAW and erroring out if non-NULL. I don't want to implement > "U-Boot environment in NAND".
How about using the second erase page for the command line ? That way, it doesn't conflict with anything a u-boot based system puts into the NAND, and you have a reasonably good chance that the location will be usable. NAND needs a command line if you want to allow people to switch back and forth between Qi and u-boot, i.e., share kernel and rootfs locations with u-boot, because of the evil dynamic partitions. The hard-coded defaults in Qi are only correct if you don't have any bad blocks in the first ~9MB, the probability of which may be as low as 24% if Samsung max out their bad block allowance. At least the chance that the kernel is at the expected place (but rootfs may not) is 94.4% or better. In any case, I would recommend that anyone installing Qi should first check that their partition sizes are 0x40000, 0x40000, 0x800000, 0xa0000, and 0x40000. (Command "mtd" in u-boot or "cat /proc/mtd" in Linux.) - Werner
