All of lore.kernel.org
 help / color / mirror / Atom feed
From: Priyanka Jain <priyanka.jain@nxp.com>
To: u-boot@lists.denx.de
Subject: [PATCH] armv8: fsl-layerscape: Fix automatic setting of bootmcd with TF-A
Date: Fri, 11 Dec 2020 07:56:17 +0000	[thread overview]
Message-ID: <VE1PR04MB649445DC3D7A54131B3DF96EE6CA0@VE1PR04MB6494.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20201117152004.58980-1-alban.bedel@aerq.com>

>-----Original Message-----
>From: Alban Bedel <alban.bedel@aerq.com>
>Sent: Tuesday, November 17, 2020 8:50 PM
>To: u-boot at lists.denx.de
>Cc: Priyanka Jain <priyanka.jain@nxp.com>; Pankit Garg
><pankit.garg@nxp.com>; Bedel, Alban <alban.bedel@aerq.com>
>Subject: [PATCH] armv8: fsl-layerscape: Fix automatic setting of bootmcd with
>TF-A
>
>When booting from TF-A there is a logic that attempt to detect if the default
>environment is used, if this is the case it then set the `bootcmd` and
>`mcinitcmd` depending of the device we booted from.
>This detection logic is dubious as it access internals of the env implementation
>and it doesn't always work correctly.
>
>First of all it detect any valid environment as not being the default, so after
>running `env default -a && saveenv` the board doesn't boot anymore as
>`bootcmd` is then empty.
>But it also fails in some other ways, for example it always detect a default
>environment when redundant env is enabled on MMC, so in that case
>`bootcmd` is overwritten on every boot.
>
>Instead of increasing the complexity of the detection just check if `bootcmd`
>and `mcinitcmd` are set in the environment and set them if they are not.
>
>Signed-off-by: Alban Bedel <alban.bedel@aerq.com>
>---
<snip>
Applied to fsl-qoriq. 
Awaiting upstream

Regards
Priyanka

      reply	other threads:[~2020-12-11  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-17 15:20 [PATCH] armv8: fsl-layerscape: Fix automatic setting of bootmcd with TF-A Alban Bedel
2020-12-11  7:56 ` Priyanka Jain [this message]

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=VE1PR04MB649445DC3D7A54131B3DF96EE6CA0@VE1PR04MB6494.eurprd04.prod.outlook.com \
    --to=priyanka.jain@nxp.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 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.