public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] How to add device tree support to a board?
Date: Thu, 21 Jun 2007 21:22:06 -0400	[thread overview]
Message-ID: <467B243E.2020508@gmail.com> (raw)
In-Reply-To: <20070621164721.92910@gmx.net>

Gerhard Pircher wrote:
> Hi,
> 
> I'm trying to understand how to add flatten device tree support to
> a specific board (MAI/AmigaOneG3SE in this case). Besides setting
> CONFIG_OF_LIBFDT, is it necessary to add any code to the board's
> platform code? Which nodes are automatically added to the fdt by
> U-boot? Does the device tree include nodes for e.g. the PCI bus
> and its devices?
> 
> regards,
> 
> Gerhard
> 
> PS: Please put me on CC:

Hi Gerhard,

It is hard to say.  I've done the Freescale MPC8360EMDS eval board, 
which is a whole different animal than an AmigaOneG3SE (and I don't know 
exactly what an AmigaOneG3SE is).  If you don't have any 
fixups/additions necessary for the fdt, then it theoretically is "enable 
and it just works" but you will be blazing new ground and I wouldn't bet 
on it being quite that simple.  It never seems to be. :-/

If you look at my page FDT page, you will see a table of known 
conversions, most of which have not happened yet (only the MPC8360 
family has been worked on).
   <http://www.denx.de/wiki/UBoot/UBootFdtInfo#adapt>

There are three areas that fix up fdt entries: board setup, CPU setup, 
and PCI setup.  These do fixups on things like ethernet MAC addresses 
(set them from the env variables) and clock frequencies.  I would guess 
that your AmigaOneG3SE won't need these fixed up, with the possible 
exception of the MAC addresses.  The current boards that have fixups 
have different boards and/or configurations that can run with different 
PCI and CPU clock frequencies, for instance, so the fdt property has to 
be fixed up with the correct frequency for the given configuration.

FWIIW, I'm coming out of my busy cycle of the month (first 2+ weeks) and 
am getting ready to update the u-boot-fdt fork with respins of some of 
the existing patches and some improvements (primarily addressing Kim's 
concerns).  I hope to get this published and pushed to the u-boot-fdt 
repo this week, probably spilling into next week.

Good luck,
gvb

  reply	other threads:[~2007-06-22  1:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 16:47 [U-Boot-Users] How to add device tree support to a board? Gerhard Pircher
2007-06-22  1:22 ` Jerry Van Baren [this message]
2007-06-22 12:40   ` Gerhard Pircher
2007-06-22 18:32     ` Jerry Van Baren

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=467B243E.2020508@gmail.com \
    --to=gvb.uboot@gmail.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