From mboxrd@z Thu Jan 1 00:00:00 1970 From: Hans de Goede Date: Thu, 16 Oct 2014 11:28:18 +0200 Subject: [U-Boot] ARM: bootm: Allow booting in secure mode on hyp capable systems In-Reply-To: <1413367985-4365-1-git-send-email-hdegoede@redhat.com> References: <1413367985-4365-1-git-send-email-hdegoede@redhat.com> Message-ID: <543F8FB2.8000609@redhat.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Hi, On Oct. 15, 2014, 10:25 a.m., Albert ARIBAUD wrote: > Hi Marc, Hans, > > On Wed, 15 Oct 2014 11:18:28 +0100, Marc Zyngier > wrote: > > > On Wed, Oct 15 2014 at 11:13:05 AM, Hans de Goede wrote: > > > Older Linux kernels will not properly boot in hype mode, add support for a > > > bootm_boot_mode environment variable, which when set to "sec" will cause > > > u-boot to boot in secure mode even when build with non-sec (and hyp) support. > > > > > > Signed-off-by: Hans de Goede > > > > Looks good to me. > > > > Acked-by: Marc Zyngier > > > > M. > > Should we consider this a bugfix? This is not really a bug fix, this adds a mechanism to select between secure / non secure boot on non-secure boot capable systems, as some older kernels do not work in non-secure mode. Even with this in place old (broken) kernels will still not magically work. Some sunxi specific patches are needed for that, as well as the user actually setting the environment variable. I'm targetting the next u-boot release for getting old sunxi kernels to work for people who prefer using those kernels. > For instance, hHow old are these "older kernels"? The linux-sunxi kernel I'm specifically targetting is a 3.4 kernel, but this should be useful in general on all platforms which support booting in non-secure mode. Regards, Hans