From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bartlomiej Sieka Date: Thu, 17 Jan 2008 20:43:18 +0100 Subject: [U-Boot-Users] RFC: new bootm syntax v2 In-Reply-To: <478FAE9E.7040005@semihalf.com> References: <477CB301.8070207@semihalf.com> <478FAE9E.7040005@semihalf.com> Message-ID: <478FAFD6.7090103@semihalf.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Bartlomiej Sieka wrote: > [...] >> As part of adding support for the new uImage format, bootm command will >> be reworked quite a bit. Below is a note that summarizes bootm usage >> scenarios (present and planned), and defines extensions to bootm >> arguments' syntax. The note, or its portions, can be later on added to >> the tree as documentation. > > Here's a revised note, with the following changes from the first version: > - addressed Wolfgang's comments posted to the list > - dropped support for standalone applications from bootm > > Looking forward to any comments, questions, etc. Hmm, seems like a portion of the note with new syntax and examples got lost somehow. I'm resending entire note below, please disregard previous attempt. Regards, Bartlomiej New syntax for bootm (v2) ========================= As part of adding support for new uImage format, bootm command (and other commands as well) will have to understand new syntax of the arguments. This is necessary in order to specify objects contained in the new uImage, on which bootm has to operate. This note attempts to first summarize both current and future bootm usage scenarios, and then introduces new argument syntax. bootm usage scenarios --------------------- Below is a summary of bootm usage scenarios, focused on booting a PowerPC Linux kernel. Some of the scenarios exist and are supported already, some will be extended/added along with the new uImage format. The purpose of the following list is to document a complete list of supported bootm usages. Note: U-Boot supports two methods of booting a PowerPC Linux kernel: old way, i.e., without passing the Flattened Device Tree (FDT), and new way, where the kernel is passed a pointer to the FDT. The boot method is indicated for each scenario. 1. bootm boot image at the current address, equivalent to 2,3,8 Old uImage: 2. bootm /* single image at */ 3. bootm /* multi-image at */ 4. bootm - /* multi-image at */ 5. bootm /* single image at */ 6. bootm /* single image at */ 7. bootm - /* single image at */ New uImage: 8. bootm 9. bootm []: 10. bootm []# 11. bootm []: []: 12. bootm []: []: []: 13. bootm []: []: 14. bootm []: - []: 15. bootm []: - Ad. 1. This is equivalent to cases 2,3,8, depending on the type of image at the current image address. - boot method: see cases 2,3,8 Ad. 2. Boot kernel image located at . - boot method: non-FDT Ad. 3. First and second components of the image at are assumed to be a kernel and a ramdisk, respectively. The kernel is booted with initrd loaded with the ramdisk from the image. - boot method: depends on the number of components at , and on whether U-Boot is compiled with OF support: | 2 components | 3 components | | (kernel, initrd) | (kernel, initrd, fdt) | --------------------------------------------------------------------- #ifdef CONFIG_OF_* | non-FDT | FDT | #ifndef CONFIG_OF_* | non-FDT | non-FDT | Ad. 4. Similar to case 3, but the kernel is booted without initrd. Second component of the multi-image is irrelevant (it can be a dummy, 1-byte file). Note: currently, U-Boot compiled without OF support does not handle this case properly, this shall be fixed along with adding support for new uImage. - boot method: see case 3 Ad. 5. Boot kernel image located at with initrd loaded with ramdisk from the image at . - boot method: non-FDT Ad. 6. is the address of a kernel image, is the address of a ramdisk image, and is the address of a FDT binary blob. Kernel is booted with initrd loaded with ramdisk from the image at . - boot method: FDT Ad. 7. is the address of a kernel image and is the address of a FDT binary blob. Kernel is booted without initrd. - boot method: FDT Ad. 8. Image at is assumed to contain a default configuration, which is booted. - boot method: FDT or non-FDT, depending on whether the default configuration defines FDT Ad. 9. Similar to case 2: boot kernel stored in from the image at address . - boot method: non-FDT Ad. 10. Boot configuration from the image at . - boot method: FDT or non-FDT, depending on whether the configuration given defines FDT Ad. 11. Equivalent to case 5: boot kernel stored in from the image at with initrd loaded with ramdisk from the image at . - boot method: non-FDT Ad. 12. Equivalent to case 6: boot kernel stored in from the image at with initrd loaded with ramdisk from the image at , and pass FDT blob from the image at . - boot method: FDT Ad. 13. Similar to case 12, the difference being that is the address of FDT binary blob that is to be passed to the kernel. - boot method: FDT Ad. 14. Equivalent to case 7: boot kernel stored in from the image at , without initrd, and pass FDT blob from the image at . - boot method: FDT Ad. 15. Similar to case 14, the difference being that is the address of the FDT binary blob that is to be passed to the kernel. - boot method: FDT Note on current image address ----------------------------- When bootm is called without arguments, the image at current image address is booted. The current image address is the address set most recently by a load command, etc, and is by default equal to CFG_LOAD_ADDR. For example, consider the following commands: tftp 200000 /tftpboot/kernel bootm Last command is equivalent to: bootm 200000 In case of the new uImage argument syntax, the address portion of any argument can be omitted. If is omitted, then it is assumed that image at should be used. Similarly, when is omitted, is is assumed that image at should be used. If is omitted, it is assumed that the current image address is to be used. For example consider the following commands: tftp 200000 /tftpboot/uImage bootm :kernel at 1 Last command is equivalent to: bootm 200000:kernel at 1 tftp 200000 /tftpboot/uImage bootm 400000:kernel at 1 :ramdisk at 1 Last command is equivalent to: bootm 400000:kernel at 1 400000:ramdisk at 1 tftp 200000 /tftpboot/uImage bootm :kernel at 1 400000:ramdisk at 1 :fdt at 1 Last command is equivalent to: bootm 200000:kernel at 1 400000:ramdisk at 1 400000:fdt at 1 New argument syntax ------------------- New uImage support introduces two new forms for bootm arguments, with the following syntax: - new uImage sub-image specification : - new uImage configuration specification # Examples: - boot kernel "kernel at 1" stored in a new uImage located at 200000: bootm 200000:kernel at 1 - boot configuration "cfg at 1" from a new uImage located at 200000: bootm 200000#cfg at 1 - boot "kernel at 1" from a new uImage at 200000 with initrd "ramdisk at 2" found in some other new uImage stored at address 800000: bootm 200000:kernel at 1 800000:ramdisk at 2 - boot "kernel at 2" from a new uImage at 200000, with initrd "ramdisk at 1" and FDT "fdt at 1", both stored in some other new uImage located at 800000: bootm 200000:kernel at 1 800000:ramdisk at 1 800000:fdt at 1 - boot kernel "kernel at 2" with initrd "ramdisk at 2", both stored in a new uImage at address 200000, with a raw FDT blob stored at address 600000: bootm 200000:kernel at 2 200000:ramdisk at 2 600000 - boot kernel "kernel at 2" from new uImage at 200000 with FDT "fdt at 1" from the same new uImage: bootm 200000:kernel at 2 - 200000:fdt at 1