From: Marc Zyngier <marc.zyngier@arm.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: bootm: Allow booting in secure mode on hyp capable systems
Date: Wed, 15 Oct 2014 11:43:30 +0100 [thread overview]
Message-ID: <86bnpd62b1.fsf@arm.com> (raw)
In-Reply-To: <E1XeLm4-0000r4-F7@janus> (Albert ARIBAUD's message of "Wed, 15 Oct 2014 11:25:43 +0100")
On Wed, Oct 15 2014 at 11:25:43 AM, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
> Hi Marc, Hans,
>
> On Wed, 15 Oct 2014 11:18:28 +0100, Marc Zyngier <marc.zyngier@arm.com>
> wrote:
>
>> On Wed, Oct 15 2014 at 11:13:05 AM, Hans de Goede <hdegoede@redhat.com> 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 <hdegoede@redhat.com>
>>
>> Looks good to me.
>>
>> Acked-by: Marc Zyngier <marc.zyngier@arm.com>
>>
>> M.
>
> Should we consider this a bugfix? For instance, hHow old are these
> "older kernels"?
No idea. Probably in the low 3.x range, for x <= 4. Not sure if that's a
bug fix though...
M.
--
Jazz is not dead. It just smells funny.
next prev parent reply other threads:[~2014-10-15 10:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 10:13 [U-Boot] [PATCH] ARM: bootm: Allow booting in secure mode on hyp capable systems Hans de Goede
2014-10-15 10:18 ` Marc Zyngier
2014-10-15 10:25 ` Albert ARIBAUD
2014-10-15 10:43 ` Marc Zyngier [this message]
2014-10-15 10:25 ` Siarhei Siamashka
2014-10-15 10:31 ` Marc Zyngier
2014-10-15 10:40 ` Siarhei Siamashka
2014-10-15 12:42 ` Marc Zyngier
2014-10-15 14:05 ` Siarhei Siamashka
2014-10-15 14:39 ` Mark Rutland
2014-10-16 2:30 ` Siarhei Siamashka
2014-10-15 16:40 ` Marc Zyngier
2014-10-16 2:13 ` Siarhei Siamashka
2014-10-16 9:28 ` [U-Boot] " Hans de Goede
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=86bnpd62b1.fsf@arm.com \
--to=marc.zyngier@arm.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