Dear Stefano Babic,
In message <1272455915-1143-1-git-send-email-sba...@denx.de> you wrote:
> Because the the size of u-boot increased after adding
> new features (mainly the support for ubi/ubifs), storing
> u-boot requires an additional sector on the flash. The patch
> adjusts the kernel_addr and mtdparts variables giving 128KB
> more space for u-boot code.
...
> @@ -144,7 +144,7 @@
> "addmtd=setenv bootargs ${bootargs} ${mtdparts}\0" \
> "addmisc=setenv bootargs ${bootargs}\0" \
> "uboot_addr=a0000000\0" \
> - "kernel_addr=a0080000\0" \
> + "kernel_addr=a00a0000\0" \
> "ramdisk_addr=a0300000\0" \
=========^^^^^^^^^^^^^^^^^^^^^
> "u-boot=qong/u-boot.bin\0" \
> "kernel_addr_r=80800000\0" \
> @@ -274,7 +274,7 @@ extern int qong_nand_rdy(void *chip);
> #define CONFIG_FLASH_CFI_MTD
> #define MTDIDS_DEFAULT "nor0=physmap-flash.0"
> #define MTDPARTS_DEFAULT \
> - "mtdparts=physmap-flash.0:256k(U-Boot),128k(env1)," \
> + "mtdparts=physmap-flash.0:384k(U-Boot),128k(env1)," \
> "128k(env2),2560k(kernel),13m(ramdisk),-(user)"
This shifts the start address of the "ramdisk' and "user" partitions
to some odd addresses; also, this makes the definition of
"ramdisk_addr" (see above) incorrct.
I recommend to do this instead:
- "mtdparts=physmap-flash.0:256k(U-Boot),128k(env1)," \
- "128k(env2),2560k(kernel),13m(ramdisk),-(user)"
+ "mtdparts=physmap-flash.0:384k(U-Boot),128k(env1)," \
+ "128k(env2),2432k(kernel),13m(ramdisk),-(user)"
What do you think?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de
People seldom know what they want until you give them what they ask
for.
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot
