[U-Boot] [PATCH 3/7] warp7: include: configs: Differentiate bootscript address from loadaddr

[Pierre-Jean Texier]

Le 15/05/2019 à 10:23, Bryan O'Donoghue a écrit :
>
>
> On 14/05/2019 21:27, Pierre-Jean Texier wrote:
>>>
>>> should this apply in isolation ?
>> Not necessarily, on my side everything working well on-top of master, 
>> for example:
>>
>> Hit any key to stop autoboot:  0
>> => run bootcmd_mmc0
>> switch to partitions #0, OK
>> mmc0(part 0) is current device
>> Scanning mmc 0:1...
>> Found U-Boot script /boot.scr
>
> So do you need a boot.scr for this patch to work, how will that affect 
> current users who rely on the u-boot env only ?

In fact, by using the Generic Distro Concept, we can also use the 
extlinux file, as explained in[1].
Example on WaRP7 :

=> run bootcmd_mmc0
switch to partitions #0, OK
mmc0(part 0) is current device
Scanning mmc 0:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
132 bytes read in 1 ms (128.9 KiB/s)
1:    linux
Retrieving file: /zImage
8118520 bytes read in 116 ms (66.7 MiB/s)
append: root=PARTUUID= rootwait rw console=ttymxc0,115200
Retrieving file: /imx7s-warp.dtb
26889 bytes read in 4 ms (6.4 MiB/s)
Kernel image @ 0x80800000 [ 0x000000 - 0x7be0f8 ]
## Flattened Device Tree blob at 83000000
    Booting using the fdt blob at 0x83000000
    Using Device Tree in place at 83000000, end 83009908


Regarding your question, it seems that is now the standard on many 
platforms [2].
In fact, instead of keeping a custom environment, it is better to use a 
more
generic approach by switching to disto config (with boot.scr, extlinux, 
and so on).

For sure, we can customized the CONFIG_BOOTCOMMAND variable in patch.


[1] http://git.denx.de/?p=u-boot.git;a=blob;f=doc/README.distro
[2] 
https://github.com/u-boot/u-boot/search?q=BOOT_TARGET_DEVICES%28func%29&unscoped_q=BOOT_TARGET_DEVICES%28func%29

Thanks

Pierre-jean