All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Booting a dt zImage kernel
Date: Mon, 23 Apr 2012 17:21:14 +0200	[thread overview]
Message-ID: <4F95736A.7070604@denx.de> (raw)
In-Reply-To: <CAOMZO5A5gzCFU8CQUXfcTUB3qKKcUVPnDHuKNk4oXDhx2aO8gA@mail.gmail.com>

On 23/04/2012 16:13, Fabio Estevam wrote:
> Hi,
> 

Hi Fabio,

> I am able to successfully boot a zImage kernel with latest 2012.04
> U-boot on mx28evk.
> 
> Now I want to boot a dt zImage version.
> 
> These are the steps I am doing:
> 
> make menuconfig and select [*] Support MXS platforms from device tree
> 
> make imx28-evk.dtb
> 
> make
> 
> cat arch/arm/boot/imx28-evk.dtb arch/arm/boot/zImage > arch/arm/boot/zImage_dtb

Is it possible ? Do you not set CONFIG_ARM_APPENDED_DTB in kernel and
let kbuild doing the rest of the job ?

Is there some reason doing this ? I mean, the easy and tested way is to
produce an uImage, and start the kernel from U-Boot with "bootm
<address> - <dtb in ram>". Of course, CONFIG_OF_LIBFDT must be enabled,
it is currently not set in mainline for mx28.

Best regards,
Stefano Babic

-- 
=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic at denx.de
=====================================================================

      parent reply	other threads:[~2012-04-23 15:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 14:13 [U-Boot] Booting a dt zImage kernel Fabio Estevam
2012-04-23 14:26 ` Marek Vasut
2012-04-23 14:50 ` Shawn Guo
2012-04-23 15:29   ` Fabio Estevam
2012-04-23 15:41     ` Stephen Warren
2012-04-23 15:46       ` Fabio Estevam
2012-04-23 15:21 ` Stefano Babic [this message]

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=4F95736A.7070604@denx.de \
    --to=sbabic@denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.