public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Agner <stefan@agner.ch>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v1] colibri_imx7: boot kernel in secure mode
Date: Wed, 24 Jul 2019 13:32:42 +0200	[thread overview]
Message-ID: <5cea7bd07d31801ae20cd6841d4d75c2@agner.ch> (raw)
In-Reply-To: <20190703135028.19271-1-igor.opaniuk@gmail.com>

On 2019-07-03 15:50, Igor Opaniuk wrote:
> From: Igor Opaniuk <igor.opaniuk@toradex.com>
> 
> NXP downstream kernel uses legacy method to enable other cores,
> which requires kernel to run in a security mode (althought upstream kernel
> uses PSCI for this).
> 
> As we're using NXP kernel in our BSPs, lets enable this by default.

I think I mentioned it internally, but just to be clear: I do not agree
with this patch.

Upstream U-Boot should be able to boot upstream Linux. I'd rather prefer
to carry that patch in our downstream fork (or set the bootm_boot_mode
environment in our boot script).

--
Stefan

> 
> Signed-off-by: Igor Opaniuk <igor.opaniuk@toradex.com>
> ---
> 
>  include/configs/colibri_imx7.h | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/include/configs/colibri_imx7.h b/include/configs/colibri_imx7.h
> index 40173b18fa..5408577661 100644
> --- a/include/configs/colibri_imx7.h
> +++ b/include/configs/colibri_imx7.h
> @@ -164,7 +164,8 @@
>  		"${board}/flash_blk.img && source ${loadaddr}\0" \
>  	"setup=setenv setupargs " \
>  		"console=tty1 console=${console}" \
> -		",${baudrate}n8 ${memargs} consoleblank=0\0" \
> +		",${baudrate}n8 ${memargs} consoleblank=0; " \
> +		"setenv bootm_boot_mode sec\0" \
>  	"setupdate=run setsdupdate || run setusbupdate || run setethupdate\0" \
>  	"setusbupdate=usb start && setenv interface usb && " \
>  		"fatload ${interface} 0:1 ${loadaddr} " \

  parent reply	other threads:[~2019-07-24 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-03 13:50 [U-Boot] [PATCH v1] colibri_imx7: boot kernel in secure mode Igor Opaniuk
2019-07-10 12:19 ` Philippe Schenker
2019-07-10 12:35   ` Tobias Junghans
2019-07-10 13:01     ` Philippe Schenker
2019-07-11 14:11     ` Igor Opaniuk
2019-07-23 13:29       ` Tobias Junghans
2019-07-24  1:29         ` Peng Fan
2019-07-24 11:29         ` Stefan Agner
2019-07-11 14:44   ` Philippe Schenker
2019-07-24 11:32 ` Stefan Agner [this message]
2019-07-24 12:19   ` Igor Opaniuk
2019-08-01 13:19     ` Stefano Babic
2019-08-01 13:23       ` Igor Opaniuk

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=5cea7bd07d31801ae20cd6841d4d75c2@agner.ch \
    --to=stefan@agner.ch \
    --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