doc/uImage.FIT/command_syntax_extensions.txt

14 ---------------------
20 Note: U-Boot supports two methods of booting a PowerPC Linux kernel: old way,
26 1.  bootm		boot image at the current address, equivalent to 2,3,8
30 3.  bootm <addr1>		    /* multi-image at <addr1>  */
31 4.  bootm <addr1> -		    /* multi-image at <addr1>  */
34 7.  bootm <addr1> -	  <addr3>   /* single image at <addr1> */
39 10. bootm [<addr1>]#<conf>[#<extra-conf[#...]]
43 14. bootm [<addr1>]:<subimg1> -			  [<addr3>]:<subimg3>
44 15. bootm [<addr1>]:<subimg1> -			  <addr3>
48 the current image address.
49 - boot method: see cases 2,3,8
52 - boot method: non-FDT
57 - boot method: depends on the number of components at <addr1>, and on whether
58   U-Boot is compiled with OF support:
62 ---------------------------------------------------------------------
63 #ifdef CONFIG_OF_*  |		    non-FDT |			FDT |
64 #ifndef CONFIG_OF_* |		    non-FDT |		    non-FDT |
67 component of the multi-image is irrelevant (it can be a dummy, 1-byte file).
68 - boot method: see case 3
72 - boot method: non-FDT
74 Ad. 6. <addr1> is the address of a kernel image, <addr2> is the address of a
75 ramdisk image, and <addr3> is the address of a FDT binary blob.  Kernel is
77 - boot method: FDT
79 Ad. 7. <addr1> is the address of a kernel image and <addr3> is the address of
81 - boot method: FDT
85 - boot method: FDT or non-FDT, depending on whether the default configuration
89 address <addr1>.
90 - boot method: non-FDT
93 - boot method: FDT or non-FDT, depending on whether the configuration given
99 - boot method: non-FDT
104 - boot method: FDT
106 Ad. 13. Similar to case 12, the difference being that <addr3> is the address
108 - boot method: FDT
113 - boot method: FDT
115 Ad. 15. Similar to case 14, the difference being that <addr3> is the address
117 - boot method: FDT
121 --------------------------
126 - new uImage sub-image specification
127 <addr>:<sub-image unit_name>
129 - new uImage configuration specification
132 - new uImage configuration specification with extra configuration components
141 - boot kernel "kernel@1" stored in a new uImage located at 200000:
144 - boot configuration "cfg@1" from a new uImage located at 200000:
147 - boot configuration "cfg@1" with extra "cfg@2" from a new uImage located
151 - boot "kernel@1" from a new uImage at 200000 with initrd "ramdisk@2" found in
152   some other new uImage stored at address 800000:
155 - boot "kernel@2" from a new uImage at 200000, with initrd "ramdisk@1" and FDT
159 - boot kernel "kernel@2" with initrd "ramdisk@2", both stored in a new uImage
160   at address 200000, with a raw FDT blob stored at address 600000:
163 - boot kernel "kernel@2" from new uImage at 200000 with FDT "fdt@1" from the
165 bootm 200000:kernel@2 - 200000:fdt@1
168 Note on current image address
169 -----------------------------
171 When bootm is called without arguments, the image at current image address is
172 booted. The current image address is the address set most recently by a load
181 In case of the new uImage argument syntax, the address portion of any argument
185 current image address is to be used. For example, consider the following