public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [linux-sunxi] [UBOOT] Both Linux-Sunxi and Mainline Uboot have issues
Date: Thu, 19 Feb 2015 10:24:50 +0100	[thread overview]
Message-ID: <54E5ABE2.7000103@redhat.com> (raw)
In-Reply-To: <1424337721.30924.5.camel@hellion.org.uk>

Hi,

On 19-02-15 10:22, Ian Campbell wrote:
> 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?

Correct, doing:

setenv bootm_boot_mode sec

Before calling "bootm" also is a way to boot old kernels on A20 devices.

>>   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)

IIRC someone took a quick look and this was non trivial, but yeah this would
really be the best thing to do, so that we can drop the old kernel compat
u-boot config at one point.

Regards,

Hans

  reply	other threads:[~2015-02-19  9:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3a04b33c-b203-4cff-bae8-6d0b5d2070d0@googlegroups.com>
2015-02-19  8:11 ` [U-Boot] [linux-sunxi] [UBOOT] Both Linux-Sunxi and Mainline Uboot have issues Hans de Goede
2015-02-19  9:22   ` Ian Campbell
2015-02-19  9:24     ` Hans de Goede [this message]
     [not found] ` <20150219143858.7aea037e@i7>
2015-02-19 13:57   ` Hans de Goede
2015-02-20  8:34     ` Siarhei Siamashka
2015-03-08  1:49   ` Siarhei Siamashka

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=54E5ABE2.7000103@redhat.com \
    --to=hdegoede@redhat.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