public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Vitaly Bordug <vitb@kernel.crashing.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Moving from arch/ppc to arch/powerpc
Date: Mon, 10 Dec 2007 17:10:55 +0300	[thread overview]
Message-ID: <20071210171055.0b4098b2@kernel.crashing.org> (raw)
In-Reply-To: <f75c52840712100116vf75d55fo5ebaa6d3bbd6419e@mail.gmail.com>

On Mon, 10 Dec 2007 09:16:41 +0000
Richard Danter wrote:

> Hi all,
> 
> Very quick question (I hope). I have U-Boot running on a board booting
> an arch/ppc kernel. The U-Boot version is pre-DTB. If I want DTB
> support in U-Boot, is it just a matter of re-compiling with a newer
> version of U-Boot or are there board-specific changes needed (assuming
> a DTB-supported CPU in use)?
> 
it should be pretty apparent (since many fsl boards and some amcc 4xx have all necessities already).

Normally,
+#define CONFIG_OF_LIBFDT 1
+#define CONFIG_OF_BOARD_SETUP 1
+#define OF_CPU "<your CPU node>"

should be enough, if you CPU family have necessary fdt hook-ups, or you may need add a few lines to
BSP code.

> Thanks
> Rich
> 
> -------------------------------------------------------------------------
> SF.Net email is sponsored by: 
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users


-- 
Sincerely, Vitaly

  parent reply	other threads:[~2007-12-10 14:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10  9:16 [U-Boot-Users] Moving from arch/ppc to arch/powerpc Richard Danter
2007-12-10 13:39 ` Josh Boyer
2007-12-10 14:10 ` Vitaly Bordug [this message]
2007-12-10 16:50 ` Clemens Koller

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=20071210171055.0b4098b2@kernel.crashing.org \
    --to=vitb@kernel.crashing.org \
    --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