FDT without FIT?

Hi list,

I'am a bit stuck here.

How can FDT be used without a FIT image?

I can't really get this from the code - if someone can point me in the right direction this would be great!

Thanks!
Simon

Dear Simon Schwarz,

I don't understand this question - using the FDT and the image format are orthogonal to each other.

Try:
help bootm

For example:

	tftp 600000 uImage
	tftp 900000 board.dtb
	bootm 600000 - 900000

What exactly is your problem?

Best regards,

Wolfgang Denk

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"Unix is simple, but it takes a genius to understand the simplicity."
					             - Dennis Ritchie

Dear Wolfgang Denk,

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)

Thanks - john already pointed me to this. This works. It was/is just a problem with the help text - duno why..

Regards
Simon

Dear Simon Schwarz,

You must either have a very old version of U-Bot, or one without FDT support built in.

Hm... I get this:

=> 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
===> When booting a Linux kernel which requires a flat device-tree
===> a third argument is required which is the address of the
===> device-tree blob. To boot that kernel without an initrd image,
===> use a '-' for the second argument. If you do not pass a third
===> a bd_info struct will be passed instead

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
ramdisk - relocate initrd, set env initrd_start/initrd_end
===> fdt - relocate flat device tree
cmdline - OS specific command line processing/setup
bdt - OS specific bd_t processing
prep - OS specific prep before relocation or go
go - start OS

Best regards,

Wolfgang Denk

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
... bacteriological warfare ... hard to believe we were once foolish
enough to play around with that.
	-- McCoy, "The Omega Glory", stardate unknown