linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@freescale.com>
To: Fredrik Roubert <roubert@df.lth.se>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: How to move from /ppc/ to /powerpc/
Date: Tue, 12 Sep 2006 10:58:30 -0500	[thread overview]
Message-ID: <20060912105830.3923d537.kim.phillips@freescale.com> (raw)
In-Reply-To: <20060912153316.GC16340@igloo.df.lth.se>

On Tue, 12 Sep 2006 17:33:16 +0200
Fredrik Roubert <roubert@df.lth.se> wrote:

> Hi!
> 
> I have a custom board on which I currently run Linux 2.6.18-rc6
> configured for MPC834x_SYS in the /ppc/ tree, which just a few minor
> changes. Now I'm interested to move to using the /powerpc/ source tree
> instead, but I can't figure out exactly what steps are necessary to do
> this.
> 
> Does anyone run a MPC834x_SYS built with ARCH=powerpc?
> 
yes

> I boot the board with U-Boot (version 1.1.4, customized), and I assume
> that I need to add some stuff for this new device tree thing, but I
> can't figure out exactly what the kernel will expect.

the kernel expects a pointer to a device tree instead of a bd_t.  The 8349EMDS device tree source is now in linux/arch/powerpc/boot/dts.  You'll need the device tree compiler (dtc) from jdl.com to build your flat device tree binary (dtb; what the kernel expects).

> 
> Does anyone have some pointers on how to do this?
> 
Matt's u-boot patches address the issue well for 85xx, they are straightforward to adapt to 83xx:

http://sourceforge.net/mailarchive/forum.php?thread_id=15518792&forum_id=12898

they allow you to tftp the dtb into mem, and "bootm ${loadaddr} - ${oftaddr}" to start an ARCH=powerpc kernel. 

> Cheers // Fredrik Roubert

Kim

  reply	other threads:[~2006-09-12 15:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 15:33 How to move from /ppc/ to /powerpc/ Fredrik Roubert
2006-09-12 15:58 ` Kim Phillips [this message]
2006-09-12 16:03   ` Jon Loeliger
2006-09-13 13:28   ` Fredrik Roubert
2006-09-13 14:46     ` Jon Loeliger
2006-09-13 17:07     ` Matthew McClintock
2006-09-21 16:08     ` Fredrik Roubert
2006-09-25 16:49       ` Matthew McClintock
2006-09-25 17:17         ` Fredrik Roubert
2006-09-25 17:20           ` Matthew McClintock
2006-09-25 17:41             ` Fredrik Roubert
2006-09-25 18:59               ` Matthew McClintock
2006-09-27 14:49                 ` Fredrik Roubert
2006-09-27 15:51     ` Fredrik Roubert
2006-09-12 16:20 ` Vitaly Bordug
  -- strict thread matches above, loose matches on Subject: below --
2006-09-13  6:58 Claus Gindhart
2006-09-13 13:30 ` Fredrik Roubert
2006-09-13 14:07 Claus Gindhart
2006-09-25 16:56 Joakim Tjernlund

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=20060912105830.3923d537.kim.phillips@freescale.com \
    --to=kim.phillips@freescale.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=roubert@df.lth.se \
    /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;
as well as URLs for NNTP newsgroup(s).