[U-Boot] arm: socfpga: Repair SoCrates board

[Jan Viktorin]

Hello Marek, Stefan, Dinh, all,

(I'm sorry If you've received this mail twice, I used a second e-mail
by mistake. This one should go to the mailing-list.)

I have a couple of short questions bellow...

On Fri, 20 Nov 2015 17:17:33 +0100
Marek Vasut <marex at denx.de> wrote:

> [snip]
> +/* Booting Linux */
> +#define CONFIG_BOOTDELAY	3
> +#define CONFIG_BOOTFILE		"zImage"

This is quite a general question. Why would one prefer zImage over
uImage (or vice-versa)? Is there some mainstream idea with this? Or is
it selected at random?

> +#define CONFIG_BOOTARGS		"console=ttyS0," __stringify(CONFIG_BAUDRATE)
> +#define CONFIG_BOOTCOMMAND	"run mmcload; run mmcboot"
> [snip]
> +
> +#define CONFIG_EXTRA_ENV_SETTINGS \
> +	"verify=n\0" \
> +	"loadaddr= " __stringify(CONFIG_SYS_LOAD_ADDR) "\0" \
> +	"ramboot=setenv bootargs " CONFIG_BOOTARGS ";" \
> +		"bootm ${loadaddr} - ${fdt_addr}\0" \
> +	"bootimage=zImage\0" \
> +	"fdt_addr=100\0" \
> +	"fdtimage=socfpga.dtb\0" \
> +		"fsloadcmd=ext2load\0" \
> +	"bootm ${loadaddr} - ${fdt_addr}\0" \
> +	"mmcroot=/dev/mmcblk0p2\0" \
> [snip]
> +	"mmcload=mmc rescan;" \
> +		"load mmc 0:1 ${loadaddr} ${bootimage};" \
> +		"load mmc 0:1 ${fdt_addr} ${fdtimage}\0" \

The FAT partition is supposed to be the first and the Linux one as the
second. So the boot partition is to be placed at the end of the SD card.

I find it quite weird as it makes the fdisk call more complex then
necessary. I have to compute the position of the boot partition based
on the size of the SD card. If I just create the paritions in the (say)
natural order a2, b, 83 everything is pretty straight-forward.

So, what is the reason of this? Why anybody likes to use such layout?

Thanks
Jan Viktorin


-- 
   Jan Viktorin                  E-mail: Viktorin at RehiveTech.com
   System Architect              Web:    www.RehiveTech.com
   RehiveTech
   Brno, Czech Republic