From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 5/5] pico-imx7d: Add bl33 config
Date: Tue, 26 Mar 2019 09:23:18 -0300 [thread overview]
Message-ID: <CAP9ODKqK3L7pTuM6FaoG9ZwCW2NZx+k8k9ko+ySSXYpz+FKCuA@mail.gmail.com> (raw)
In-Reply-To: <1553592073-20154-6-git-send-email-jun.nie@linaro.org>
On Tue, Mar 26, 2019 at 6:23 AM Jun Nie <jun.nie@linaro.org> wrote:
>
> Add default configuration to run u-boot as BL33 in the boot flow case
> of ATF(ARM Trusted Firmware) -> OPTEE -> U-boot.
>
> Signed-off-by: Jun Nie <jun.nie@linaro.org>
Please base it on pico-imx7d_defconfig so user is asked for the base
board to use and it provides more flexibility to test.
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854 Mobile: +1 (347) 903-9750
next prev parent reply other threads:[~2019-03-26 12:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 9:21 [U-Boot] [PATCH 0/5] pico-imx7d: Add support for BL33 case Jun Nie
2019-03-26 9:21 ` [U-Boot] [PATCH 1/5] mx7_common: Share configs to skip low level init Jun Nie
2019-03-26 9:21 ` [U-Boot] [PATCH 2/5] imx: mx7: Add empty arch_cpu_init if skipped Jun Nie
2019-03-26 9:21 ` [U-Boot] [PATCH 3/5] pico-imx7d: Reserve region of memory to OPTEE Jun Nie
2019-03-26 9:21 ` [U-Boot] [PATCH 4/5] pico-imx7d: Add boot option for verified boot Jun Nie
2019-03-26 9:21 ` [U-Boot] [PATCH 5/5] pico-imx7d: Add bl33 config Jun Nie
2019-03-26 12:23 ` Otavio Salvador [this message]
2019-03-26 15:11 ` Jun Nie
2019-03-27 4:05 ` Jun Nie
2019-03-27 11:43 ` Otavio Salvador
2019-03-27 11:52 ` Fabio Estevam
2019-03-27 11:59 ` Jun Nie
2019-03-27 12:01 ` Otavio Salvador
2019-03-27 12:02 ` Fabio Estevam
2019-03-27 14:17 ` Jun Nie
2019-03-27 14:57 ` Fabio Estevam
2019-03-27 15:04 ` Jun Nie
2019-03-27 16:43 ` Fabio Estevam
2019-03-27 15:05 ` Otavio Salvador
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=CAP9ODKqK3L7pTuM6FaoG9ZwCW2NZx+k8k9ko+ySSXYpz+FKCuA@mail.gmail.com \
--to=otavio.salvador@ossystems.com.br \
--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.