From: Jon Medhurst (Tixy) <tixy@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, RFC] vexpress: Check TC2 firmware support before defaulting to nonsec booting
Date: Mon, 15 Aug 2016 09:37:58 +0100 [thread overview]
Message-ID: <1471250278.2902.0.camel@linaro.org> (raw)
In-Reply-To: <20160814200514.GK4188@bill-the-cat>
On Sun, 2016-08-14 at 16:05 -0400, Tom Rini wrote:
> On Thu, Jun 23, 2016 at 01:37:32PM +0100, Jon Medhurst (Tixy) wrote:
>
> > The firmware on TC2 needs to be configured appropriately before booting
> > in nonsec mode will work as expected, so test for this and fall back to
> > sec mode if required.
> >
> > Signed-off-by: Jon Medhurst <tixy@linaro.org>
> > Reviewed-by: Ryan Harkin <ryan.harkin@linaro.org>
> > Tested-by: Ryan Harkin <ryan.harkin@linaro.org>
> > ---
> >
> > This is an implementation of Andre's suggestion in
> > http://lists.denx.de/pipermail/u-boot/2016-June/258873.html
> >
> > Possibly the change to bootm.c should be in a separate patch?
> >
> > arch/arm/lib/bootm.c | 15 ++++++++++-----
> > board/armltd/vexpress/Makefile | 1 +
> > board/armltd/vexpress/vexpress_tc2.c | 33 +++++++++++++++++++++++++++++++++
> > 3 files changed, 44 insertions(+), 5 deletions(-)
> > create mode 100644 board/armltd/vexpress/vexpress_tc2.c
>
> So, this supersedes https://patchwork.ozlabs.org/patch/639232/ right?
Yes, it does.
Thanks
--
Tixy
next prev parent reply other threads:[~2016-08-15 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 14:34 [U-Boot] [PATCH] ARM: vexpress: Remove virt and nonsec support for TC2 Jon Medhurst
2016-06-22 14:53 ` Andre Przywara
2016-06-22 16:40 ` Jon Medhurst
2016-06-23 12:37 ` [U-Boot] [RFC PATCH] vexpress: Check TC2 firmware support before defaulting to nonsec booting Jon Medhurst
2016-06-28 16:25 ` Ryan Harkin
2016-08-14 20:05 ` [U-Boot] [U-Boot, RFC] " Tom Rini
2016-08-15 8:37 ` Jon Medhurst [this message]
2016-08-16 1:10 ` Tom Rini
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=1471250278.2902.0.camel@linaro.org \
--to=tixy@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.