public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] FDT without FIT?
Date: Wed, 24 Aug 2011 11:50:25 +0200	[thread overview]
Message-ID: <4E54C961.70006@gmail.com> (raw)
In-Reply-To: <20110823174544.24E43201520@gemini.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

  reply	other threads:[~2011-08-24  9:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-23 15:40 [U-Boot] FDT without FIT? Simon Schwarz
2011-08-23 17:45 ` Wolfgang Denk
2011-08-24  9:50   ` Simon Schwarz [this message]
2011-08-24 12:59     ` Wolfgang Denk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E54C961.70006@gmail.com \
    --to=simonschwarzcor@googlemail.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox