From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <ijc@hellion.org.uk>
Date: Thu, 19 Feb 2015 09:22:01 +0000
Subject: [U-Boot] [linux-sunxi] [UBOOT] Both Linux-Sunxi and Mainline
 Uboot have issues
In-Reply-To: <54E59AB2.2060101@redhat.com>
References: <3a04b33c-b203-4cff-bae8-6d0b5d2070d0@googlegroups.com>
 <54E59AB2.2060101@redhat.com>
Message-ID: <1424337721.30924.5.camel@hellion.org.uk>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Thu, 2015-02-19 at 09:11 +0100, Hans de Goede wrote:
> Note assuming you're using linux-sunxi kernels and not upstream kernels you also
> need "Enable workarounds for booting old kernels" for things to boot at all
> on A20 based devices,

IIRC there is also an env var which can be set to force booting in
secure mode?

>  because the new u-boot by default boots the kernel in
> non secure mode (so that it can be a hypervisor and hw accelerated qemu-kvm works
> on the A20), but the old kernels do not work when booted in non secure mode
> (another bug in the old kernels, for which no fix is available).

(probably some mainline commits to head.S to handle boot in hyp mode
could be backported, ignoring the actual KVM stuff)

Ian.