public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 2/5] board support of arm64
Date: Mon, 19 Aug 2013 16:43:16 -0400	[thread overview]
Message-ID: <52128364.7090401@ti.com> (raw)
In-Reply-To: <1376942351.31636.376.camel@snotra.buserror.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/19/2013 03:59 PM, Scott Wood 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.

Longer term, I want us to be able to make more use of device trees,
where possible and bindings are complete and stable.  And at that
point we'll have to deal with "how do we get a DT from $where-ever to
here to use.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSEoNhAAoJENk4IS6UOR1Wo4EQAIYz21GZOidLA3BzN1BjTmdK
irumwyi0iRZto4jEpqyr7UjOBK+cmHDq3/hhzo1Y4MlX3YezD+yPWRY+7+bk2Dl6
B8huuHaLMTuNK7AHPgMAOmbdxwaQRs8ZP8NA26YH5nvjOqGfpjhPDr+gD7qcRTCA
3RkOVuD5pB6mtdZdGCZqvRVAW9w+6pIhNJpokFmlvRIXLh48R7RAyiu3Ac1JPL8k
sIHmFDDEFhTcbsJdDB93uEIKqMM0K2enhpVB09ZxxpL+EVGwfVYoMGO3q0+2kL8y
q0uawG1vwrkniB0tV5Snp7EBSQdlRo1QIfutfNYI1QRgUEipY41Supx/OkAvaHAP
W2e8tmbq9EaU+TRV3SHn6AjBCTy4shYYv4r/mvEjdVhblxGK4MTdhUmhGKFABU/D
4odQlRXDFirImlELCKXr3qgT3oTWuPjIu9Udc6llwbkgZSteGrdTOyRtRo/xJ5H3
34EkHmFw65cW0kTAhJc91DzrIG7beRM5WVqJfviXE1X5uugJGg3LZidiFQxDPBGM
q+alr+G5Wvo+xrqnmnWeBEev24Oift0GoG4nEtKcnlsQj7i5eEbJj7u6ox7OszCb
8Jp9tVXFZ7c3ZuLh3lcKGYxSnrH81NBxC5f17q+g4pprAxgFTB4DV7WPeqUUxlQB
Hqsm3WzPEoAu5NCD3J7/
=9iEp
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-08-19 20:43 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 [this message]
2013-08-22 16:15       ` Stuart Yoder
2013-08-22 16:23         ` Scott Wood
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=52128364.7090401@ti.com \
    --to=trini@ti.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