I really like HK's boot.ini method since you don't have to "make" any .scr file. It's basically a text script for u-boot, but mainline doesn't use it. It's also great that you can edit the text file on a live system and not have to worry about changing env values in u-boot itself (having to go through uart).
Mainline seems to be doing something along the lines of syslinux (sysboot) and looks for "extlinux.conf" first. U-boot maintains compatibility with the old .scr, but it sounds like it would like to move away from it:
*README.distrothis document recommends that distros generate extlinux.conf rather than boot.scr
Also while README.odroid was updated a year ago to include xu3 changes, it doesn't say anything about extlinux.conf, and when it does mention boot options like "boot_zimg", that doesn't seem to be an option for xu3/4.
Instead boot goes something like this:
1) scan_dev_for_extlinux->boot_extlinux->sysboot mmc 0:1 any 0x50000000 /extlinux/extlinux.conf
2) scan_dev_for_scripts->boot_a_script->load mmc 0:1 0x50000000 /boot.scr;source 0x50000000
I tried "/extlinux/extlinux.conf" with:
Code: Select all
DEFAULT linux LABEL linux KERNEL ../zImagexu444R4 FDTFILE ../exynos5422-odroidxu444R4.dtb APPEND console=tty1 console=ttySAC2,115200n8 root=UUID=e139ce78-9841-40fe-8823-96a304a09859 rootwait ro fsck.repair=yes
Code: Select all
Scanning mmc 0:1... Found /extlinux/extlinux.conf Retrieving file: /extlinux/extlinux.conf reading /extlinux/extlinux.conf 211 bytes read in 4 ms (50.8 KiB/s) Ignoring unknown command: FDTFILE Ignoring unknown command: APPEND 1: linux Retrieving file: /extlinux/../zImagexu444R4 reading /extlinux/../zImagexu444R4 2869328 bytes read in 218 ms (12.6 MiB/s) Kernel image @ 0x42000000 [ 0x000000 - 0x2bc850 ] Starting kernel ...
Should I shoot an email to Hyungwon Hwang and/or Przemyslaw Marczak linking to this thread (regarding the readme.odroid)?
http://git.denx.de/?p=u-boot.git;a=comm ... fb15335d48