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: Mon, 19 Aug 2013 15:53:02 -0400	[thread overview]
Message-ID: <20130819195302.GL1311@bill-the-cat> (raw)
In-Reply-To: <yw1xwqnhh33z.fsf@unicorn.mansr.com>

On Mon, Aug 19, 2013 at 08:50:24PM +0100, M?ns Rullg?rd wrote:
> Tom Rini <trini@ti.com> writes:
> 
> > On 08/19/2013 01:33 PM, M?ns Rullg?rd wrote:
> >> Scott Wood <scottwood@freescale.com> writes:
> > [snip]
> >>> i960 is a bad analogy.  It's often possible to turn arm32 asm
> >>> into arm64 asm with some search and replace and minor manual
> >>> fixups.
> >>
> >> Only if the original uses none of the distinguishing features of
> >> ARM like predicated instructions or variably shifted operands.
> >> Once you limit yourself to the remaining basic operations, every
> >> (RISC) architecture looks the same.
> > [snip]
> >> AArch64 of course shares certain non-ISA aspects with AArch32.
> >> Page table formats and other architecturally defined system control
> >> features are the same, and code for managing these things should of
> >> course be shared.  Some other features, e.g. exception handling,
> >> are different enough that sharing code is probably difficult.
> >>
> >> There is a tendency to see arm64/aarch64 as yet another 64-bit
> >> extension of a 32-bit architecture, which it is not.  Assuming that
> >> software support will or can follow the model used by the others
> >> mentioned is thus a mistake.
> >
> > We don't have lots of hand-crafted assembly, and what we do, we
> > largely have split out already into the cpu directories.  I really
> > think we just need to try this and see how it goes.
> 
> Fine, let's see what it ends up looking like.
> 
> That said, please consider naming things in a way that armv8 does not
> imply 64-bit.

Agreed, thanks!

-- 
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/20130819/a6962f1a/attachment.pgp>

  reply	other threads:[~2013-08-19 19:53 UTC|newest]

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