From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Schwarz Date: Wed, 24 Aug 2011 11:50:25 +0200 Subject: [U-Boot] FDT without FIT? In-Reply-To: <20110823174544.24E43201520@gemini.denx.de> References: <4E53C9F6.4010609@gmail.com> <20110823174544.24E43201520@gemini.denx.de> Message-ID: <4E54C961.70006@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 Wolfgang Denk, On 08/23/2011 07:45 PM, Wolfgang Denk wrote: > Dear Simon Schwarz, > > In message<4E53C9F6.4010609@gmail.com> you wrote: >> >> How can FDT be used without a FIT image? > > I don't understand this question - using the FDT and the image format > are orthogonal to each other. > >> I can't really get this from the code - if someone can point me in the >> right direction this would be great! > > Try: > help bootm > This prints: # help bootm bootm - boot application image from memory Usage: bootm [addr [arg ...]] - boot application image stored in memory passing arguments 'arg ...'; when booting a Linux kernel, 'arg' can be the address of an initrd image Sub-commands to do part of the bootm sequence. The sub-commands must be issued in the order below (it's ok to not issue all sub-commands): start [addr [arg ...]] loados - load OS image cmdline - OS specific command line processing/setup bdt - OS specific bd_t processing prep - OS specific prep before relocation or go go - start OS (Yes, #define CONFIG_OF_LIBFDT 1 is in my board config) > For example: > > tftp 600000 uImage > tftp 900000 board.dtb > bootm 600000 - 900000 > > What exactly is your problem? Thanks - john already pointed me to this. This works. It was/is just a problem with the help text - duno why.. > > Best regards, > > Wolfgang Denk > Regards Simon