mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Raphael Poggi <poggi.raph@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v4 0/12] Add basic support for arm64
Date: Mon, 4 Jul 2016 09:27:25 +0200	[thread overview]
Message-ID: <20160704072724.GB20657@pengutronix.de> (raw)
In-Reply-To: <1467188540-76509-1-git-send-email-poggi.raph@gmail.com>

Hi Raphael,

On Wed, Jun 29, 2016 at 10:22:07AM +0200, Raphael Poggi wrote:
> This patch series introduces a basic support for arm64.
> 
> The arm64 code is merged in the current arch/arm directory.
> I try to be iterative in the merge process, and find correct solutions
> to handle both architecture at some places.
> 
> I test the patch series by compiling arm64 virt machine and arm32 vexpress-a9 and test it
> in qemu, everything seems to work.


I'm happy with te general structure now. There surely still is much work
to do for full aarch64 support, but the current state does not disturb arm32 and
I think the remaining issues can be fixed in tree. I can merge this
series if you like, or I could delay merging in case you want to
continue working on this series without having to create incremental
patches.

Finally could you provide a qemu  command line to start the image? A
patch adding Documentation/boards/aarch64-qemu-virt.rst similar to
Documentation/boards/digic.rst would be nice.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  parent reply	other threads:[~2016-07-04  7:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-29  8:22 Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 01/13] arm64: add armv8 Kconfig entries Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 02/13] arm: Makefile: rework makefile to handle armv8 Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 03/13] arm: rework lib directory to support arm64 Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 04/13] arm: cpu: add arm64 specific code Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 05/13] arm: include: system: add arm64 helper functions Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 06/13] arm: include: bitops: arm64 use generic __fls Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 07/13] arm: include: system_info: add armv8 identification Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 08/13] arm: cpu: cpuinfo: add armv8 support Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 09/13] arm: cpu: disable code portion in armv8 case Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 10/13] arm: cpu: add basic arm64 mmu support Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 11/13] arm: boards: add mach-qemu and virt64 board Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 12/13] arm: include: swab: use rigth assembly for armv8 Raphael Poggi
2016-06-29  8:22 ` [PATCH v4 13/13] uimage: add define for ARM64 architecture Raphael Poggi
2016-07-04  7:27 ` Sascha Hauer [this message]
2016-07-04  8:38   ` [PATCH v4 0/12] Add basic support for arm64 Raphaël Poggi

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=20160704072724.GB20657@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=poggi.raph@gmail.com \
    /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