From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?ISO-8859-1?Q?Andreas_Bie=DFmann?= Date: Mon, 19 Nov 2012 11:21:43 +0100 Subject: [U-Boot] [PATCH v3 1/3] Add README for the "Falcon" mode In-Reply-To: <1353316265-24430-1-git-send-email-sbabic@denx.de> References: <1352717979-6284-1-git-send-email-sbabic@denx.de> <1353316265-24430-1-git-send-email-sbabic@denx.de> Message-ID: <50AA0837.2000002@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Stefano Babic, On 19.11.2012 10:11, Stefano Babic wrote: > Simple howto to add support to a board > for booting the kernel from SPL ("Falcon" mode). > > Signed-off-by: Stefano Babic despite a small change Acked-by: Andreas Bie?mann > --- > Changes in v3: > - parameter initrd_addr was removed in V2 (Andreas Biessmann) > - added patch to fix help usage for spl export (Andreas Biessmann) > - Added empty lines (Otavio Salvador) > - add a more exhaustive description explaining that > spl export does not save into media (Lukasz Majewski). > > Changes in v2: > - spelling, language fixes (Andreas Biessman) > - rewrite some unclear sentences > - drop CONFIG_SPL_OS_BOOT_KEY > - make example with twister more exhaustive > > +Configuration > +---------------------------- > +CONFIG_CMD_SPL Enable the "spl export" command. > + The command "spl export" is then available in U-Boot > + mode > +CONFIG_SPL_OS_BOOT Activate Falcon Mode. > + A board should implement the following functions: > + > +CONFIG_SYS_SPL_ARGS_ADDR Address in RAM where the parameters must be > + copied by SPL. > + In most cases, it is + 0x100 > + > +CONFIG_SYS_NAND_SPL_KERNEL_OFFS Offset in NAND where the kernel is stored > + > +CONFIG_CMD_SPL_NAND_OFS Offset in NAND where the parameters area was saved. > + > +CONFIG_CMD_SPL_WRITE_SIZE Size of the parameters area to be copied > + > +Function that a board must implement > +------------------------------------ > + > +void spl_board_prepare_for_linux(void) : optional > + Called from SPL before starting the kernel > + > +spl_start_uboot() : required > + Returns "0" if SPL starts the kernel, "1" if U-Boot > + must be started. > + > + shouldn't we reorder that thing here (move CONFIG_SPL_OS_BOOT down to the functions)? Best regards Andreas Bie?mann