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] [U-boot] Uboot's plan for ARMv8
Date: Fri, 10 Jan 2014 09:15:49 -0500	[thread overview]
Message-ID: <20140110141549.GA5181@bill-the-cat> (raw)
In-Reply-To: <FE7ADED5C2218B4786C09CD97DC4C49FD12022@exchbj02.viatech.com.bj>

On Fri, Jan 10, 2014 at 11:02:43AM +0800, TigerLiu at viatech.com.cn wrote:

> Hi, experts:
> 
> Does U-boot have any plan to support ARMv8 SOC?

I think the short answere here is that it's not quick to merge in brand
new arch support (it's more than just adding a new SoC family, it's
adding in a new processor family too) but we're on track to have ARMv8
support in the next release.  I would then expect that..

> Nvidia has decleared 64bit SOC plan.

... any nvidia ARMv8 platforms to come in via the u-boot-tegra tree and
other ARMv8 platforms to come in via their respective platforms (if
i.MX9000, which I just made up, is where Freescale does ARMv8, it can
still go via u-boot-imx as far as I'm concerned) unless that custodian
really wants someone else to own it.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20140110/e0d04e6a/attachment.pgp>

      parent reply	other threads:[~2014-01-10 14:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  3:02 [U-Boot] [U-boot] Uboot's plan for ARMv8 TigerLiu at viatech.com.cn
2014-01-10  4:54 ` Abraham Varricatt
2014-01-10  6:08   ` Wolfgang Denk
2014-01-10  6:09 ` bhupesh.sharma at freescale.com
2014-01-10  6:54   ` TigerLiu at viatech.com.cn
2014-01-10  7:29     ` bhupesh.sharma at freescale.com
2014-01-10  8:02       ` bhupesh.sharma at freescale.com
2014-01-10 14:15 ` Tom Rini [this message]

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=20140110141549.GA5181@bill-the-cat \
    --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