From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot for 64bit ARMv8
Date: Wed, 12 Jun 2013 18:54:54 +0200 [thread overview]
Message-ID: <20130612185454.1ce57739@lilith> (raw)
In-Reply-To: <20130612163339.GF26693@bill-the-cat>
Hi Tom,
On Wed, 12 Jun 2013 12:33:39 -0400, Tom Rini <trini@ti.com> wrote:
> On Wed, Jun 12, 2013 at 06:10:06AM -0700, Richard Schmitt wrote:
>
> > Is anyone considering porting/supporting uboot for ARMv8. ?Our initial
> > investigation of boot loader support for ARMv8 indicates that the only
> > boot loader currently being targeted is UEFI. ?
> >
> > The decisions we need to make are:
> > - Do we move to UEFI on ARM?
> > - Can we leverage someone else's enablement of ARMv8?
> > - Do we provide our own enablement of ARMv8?
> >
> > Any opinions?
>
> The general push from ARM Ltd is to use UEFI. I would strongly suspect
> that there are U-Boot forks that companies that have announced they are
> doing ARMv8 chips have something as a stop-gap until they have the
> functionality they want in uEFI.
>
> I am quite open to ARMv8 support being added to U-Boot and addressing
> the concerns companies may have. Sometimes it seems like "GPLv2+" makes
> people think "Project will be moving to GPLv3, RUN AWAY!" when all it
> really means is "Project is GPLv2+, will evaluate the appropriateness of
> later versions".
This is not specific to 64-Bit ARM support, though. GPLv2+ has been
there for very long. Aren't companies educated by now? (I am quite open
to helping spread education, anyway)
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-06-12 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 13:10 [U-Boot] U-boot for 64bit ARMv8 Richard Schmitt
2013-06-12 16:33 ` Tom Rini
2013-06-12 16:54 ` Albert ARIBAUD [this message]
2013-06-12 17:47 ` Tom Rini
2013-06-12 18:49 ` Albert ARIBAUD
2014-01-23 6:44 ` TigerLiu at viatech.com.cn
2014-01-24 0:52 ` FengHua
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=20130612185454.1ce57739@lilith \
--to=albert.u.boot@aribaud.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.