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] merge arm64 to arm
Date: Sat, 17 Aug 2013 10:52:13 -0400	[thread overview]
Message-ID: <20130817145213.GS13632@bill-the-cat> (raw)
In-Reply-To: <143c290.1fff.1408cb149f7.Coremail.fenghua@phytium.com.cn>

On Sat, Aug 17, 2013 at 10:32:43PM +0800, FengHua wrote:
> 
> 
> 
> > -----????????????-----
> > ?????????: "M??ns Rullg??rd" <mans@mansr.com>
> > ????????????: 2013???8???17??? ?????????
> > ?????????: FengHua <fenghua@phytium.com.cn>
> > ??????: u-boot at lists.denx.de, trini at ti.com, scottwood at freescale.com
> > ??????: Re: merge arm64 to arm
> > 
> > FengHua <fenghua@phytium.com.cn> writes:
> > 
> > > hi tom,
> > > hi albert,
> > > yes, it's right. the u-boot could be more uniformly and maintainable
> > > if merging armv8 to arm architecture. I will try to migrate arm64 to
> > > armv8 subarchitecture of arm. do you have any other advice?
> > 
> > Why?  The architectures are vastly different, arm64 (aarch64) being only
> > loosely inspired by the 32-bit arm.  It is not like with x86/amd64 where
> > a lot of code can be shared.
> > 
> > -- 
> > M??ns Rullg??rd
> > mans at mansr.com
> 
> Of course, with a seperated architecture the arm64 code will be clear
> and simple. when it merged with arm a few file should be duplicated
> with the name "_v8" appended and many macro switch should be added.
> but most of the code will be in armv8 directory which paralleled with
> armv7. it seems that this implementation are more nice.

Exactly.  Most things will end up in arch/arm/cpu/armv8/ and we won't
have to duplicate the "hook the arch up with the rest of U-Boot" code,
which is C anyhow, for the most part.

-- 
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/20130817/91d2286c/attachment.pgp>

  reply	other threads:[~2013-08-17 14:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-17  4:54 [U-Boot] merge arm64 to arm FengHua
2013-08-17 11:35 ` Måns Rullgård
2013-08-17 14:32   ` FengHua
2013-08-17 14:52     ` Tom Rini [this message]
2013-08-17 14:55     ` Måns Rullgård
2013-08-18  1:03       ` FengHua
2013-08-19 16:34       ` Scott Wood
     [not found] <A1A6EA40F8503D48BB002B42BD65974E0A114A73@039-SN2MPN1-013.039d.mgd.msft.net>
2013-08-19 12:20 ` Tom Rini
2013-08-19 12:32   ` Måns Rullgård
2013-08-19 12:53     ` Tom Rini
2013-08-19 13:01       ` Måns Rullgård
2013-08-19 13:10         ` Tom Rini
2013-08-19 16:55           ` Scott Wood
2013-08-19 17:33             ` Måns Rullgård
2013-08-19 17:52               ` Tom Rini
2013-08-19 19:50                 ` Måns Rullgård
2013-08-19 19:53                   ` Tom Rini
2013-08-19 18:08               ` Scott Wood

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=20130817145213.GS13632@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