public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Device tree on ppc board
Date: Tue, 23 Jun 2009 16:15:24 -0500	[thread overview]
Message-ID: <4A4145EC.3070203@freescale.com> (raw)
In-Reply-To: <002401c9f445$45820740$d08615c0$@david@innes.fr>

Olivier DAVID wrote:
> I work on a custom board, MPC8248 based (my reference BSP was MPC8260ADS),
> with uboot 1.1.4 and linux 2.6.11, and works perfectly.
> 
> We have to pass to linux 2.6.27, and it is just the version from which ppc
> and powerpc has been merged,

It was merged quite a bit earlier, that's just when the old fork was 
finally discarded.

> and device tree the unique way to pass
> 'bdinfo'. The uboot version can't be more than 1.1.6,

Why not?

> the linux must be 2.6.27, 

Why 2.6.27 and not, say, 2.6.30?  You may have problems with PCI DMA in 
2.6.27, for example.  In general, it's best to go with the latest unless 
you have a specific reason otherwise.

> and I can't find the information if it's compatible.

You can boot using cuImage if you must stay with an old u-boot.  Add 
cuImage entries for your board in arch/powerpc/boot/Makefile and 
arch/powerpc/boot/wrapper, then make zImage.

> Can anybody affirm me if it's possible, and how to do it in linux 1.1.4 ?
> 
> How do we change the bdinfo structure header to device tree, is there any
> board which uses this feature ?

mpc8272ads is probably the closest board to yours; you could use its 
device tree as an example.

-Scott

  reply	other threads:[~2009-06-23 21:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 20:57 [U-Boot] Device tree on ppc board Olivier DAVID
2009-06-23 21:15 ` Scott Wood [this message]
2009-06-27  1:37 ` Kim Phillips

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=4A4145EC.3070203@freescale.com \
    --to=scottwood@freescale.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