This one looks interesting:
Quote:
bootcmd_root_mmc=setenv bootargs $(bootargs_base) root=/dev/mmcblk1p1 rw ip=none
bootcmd_root_mvn=setenv bootargs $(bootargs_base) root=/dev/mmcblk0p1 rw ip=none
|
If that is not just a "left over" from lab126 development environment, the K3 has a second eMMC block and another root file system (plus maybe another kernel?).
As can be seen in the eMMC documentation, the part has the ability to hardware host two boot partitions (three if you count the user area of the flash).
Ref:
http://drpbox.knetconnect.com/k3/KLMxGxxEHx.pdf
Page 9.
Once we get the immediate problem solved, BB can try that out for us.