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] [PATCH v3 2/5] board support of arm64
Date: Thu, 22 Aug 2013 11:23:18 -0500	[thread overview]
Message-ID: <1377188598.5029.103.camel@snotra.buserror.net> (raw)
In-Reply-To: <CALRxmdAyGmXd=xOwZenD01con9D8oGDG4=jqR8q7w3qXnc8NWg@mail.gmail.com>

On Thu, 2013-08-22 at 11:15 -0500, Stuart Yoder wrote:
> On Mon, Aug 19, 2013 at 2:59 PM, Scott Wood <scottwood@freescale.com> wrote:
> > On Fri, 2013-08-16 at 09:14 -0500, Stuart Yoder wrote:
> >> On Thu, Aug 15, 2013 at 8:47 AM,  <fenghua@phytium.com.cn> wrote:
> >> > From: David Feng <fenghua@phytium.com.cn>
> >> >
> >> > This patch provide u-boot with arm64 support. Currently, it works on
> >> > Foundation Model for armv8 or Fast Model for armv8.
> >> >
> >> > Signed-off-by: David Feng <fenghua@phytium.com.cn>
> >> > ---
> >> > Changes for v3:
> >> >     - rewrite cache.S and exception.S that partly originated from linux kernel,
> >> >       so the license should be ok.
> >> >
> >> >  board/armltd/dts/vexpress64.dts      |  215 ++++++++++++++++++++++++++++++++++
> >>
> >> Why is the device tree source in u-boot (instead of in the kernel)?
> >> Is this temporary?   It
> >> looks like this device tree is just a copy from somewhere else.
> >>
> >> Would suggest removing this from this patch series and keep the dts maintained
> >> in the Linux kernel.
> >
> > U-Boot itself uses the device tree (not just to patch up for Linux) on
> > some targets.
> >
> > Even with the way PPC uses device trees, it doesn't really make sense to
> > keep them in the kernel given that they're meant to be OS-neutral, and
> > have ties to U-Boot in terms of what gets fixed up at runtime.
> 
> It may not make sense, but that is where they are kept currently. 

For PPC.

> It doesn't make sense to maintain 2 copies of a vexpress64.dts device tree in 2 different
> places...or to maintain 1 lone device tree in u-boot.

Why does it not make sense for there to be one lone device tree in
U-Boot?

A device tree that is not used with U-Boot may not look the same, since
U-Boot is (at least on some platforms) responsible for filling in parts
of the tree, and (again on some platforms) for setting up the address
map.

> Maybe we need a git repo for device trees that could be included
> in Linux, u-boot, and other things a submodule.

Submodules can be a pain.  If we don't use them for DTC, why would we
use them for this?  Since they require extra commands, you'd be
modifying the workflow of everyone that builds U-Boot and/or Linux for
affected platforms.

-Scott

  reply	other threads:[~2013-08-22 16:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15 13:47 [U-Boot] [PATCH v3 0/5] arm64 patch fenghua at phytium.com.cn
2013-08-15 13:47 ` [U-Boot] [PATCH v3 1/5] core support of arm64 fenghua at phytium.com.cn
2013-08-15 13:47 ` [U-Boot] [PATCH v3 2/5] board " fenghua at phytium.com.cn
2013-08-16 14:14   ` Stuart Yoder
2013-08-19 19:59     ` Scott Wood
2013-08-19 20:43       ` Tom Rini
2013-08-22 16:15       ` Stuart Yoder
2013-08-22 16:23         ` Scott Wood [this message]
2013-08-22 17:44           ` Stuart Yoder
2013-08-22 17:50             ` Scott Wood
2013-08-23 19:48               ` Tom Rini
2013-08-15 13:47 ` [U-Boot] [PATCH v3 3/5] arch support 1 " fenghua at phytium.com.cn
2013-08-15 13:47 ` [U-Boot] [PATCH v3 4/5] arch support 2 " fenghua at phytium.com.cn
2013-08-15 13:47 ` [U-Boot] [PATCH v3 5/5] 64bit initrd start address support fenghua at phytium.com.cn
2013-08-15 17:26 ` [U-Boot] [PATCH v3 0/5] arm64 patch Simon Glass
2013-08-16  5:02   ` [U-Boot] about CONFIG_SYS_GENERIC_BOARD FengHua
2013-08-16 19:19     ` Scott Wood
2013-08-16 19:28     ` Simon Glass
2013-08-16 19:41       ` Tom Rini
2013-08-16  4:32 ` [U-Boot] [PATCH v3 0/5] arm64 patch Dennis Gilmore
2013-08-16 19:53   ` Scott Wood
2013-08-17  4:55     ` Sharma Bhupesh-B45370

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=1377188598.5029.103.camel@snotra.buserror.net \
    --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