From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 3/8] x86: start64: Support HOB in 64-bit U-Boot
Date: Sun, 26 Apr 2020 14:15:50 -0600 [thread overview]
Message-ID: <CAPnjgZ3LdMNzZP-QDfFT0GMfKbJYK_a38uW1RLAZQHw2NbS9hA@mail.gmail.com> (raw)
In-Reply-To: <20200422004507.2025-4-aiden.park@intel.com>
Hi Aiden,
On Tue, 21 Apr 2020 at 18:45, <aiden.park@intel.com> wrote:
>
> From: Aiden Park <aiden.park@intel.com>
>
> This will allow 64-bit U-Boot to use HOB.
>
> Signed-off-by: Aiden Park <aiden.park@intel.com>
> ---
> arch/x86/cpu/start64.S | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/x86/cpu/start64.S b/arch/x86/cpu/start64.S
> index b8ac5aab57..7faf4f6f13 100644
> --- a/arch/x86/cpu/start64.S
> +++ b/arch/x86/cpu/start64.S
> @@ -25,6 +25,11 @@ init_64bit_entry_ret:
>
> call board_init_f_init_reserve
>
> +#if defined(CONFIG_X86_RUN_64BIT_ONLY) && defined(CONFIG_USE_HOB)
> + mov %r10, %rdi
> + call set_hob_list
> +#endif
Similar question - would it be safe to always do this?
> +
> xor %rdi, %rdi
> call board_init_f
> call board_init_f_r
> --
> 2.20.1
>
Regards,
Simon
next prev parent reply other threads:[~2020-04-26 20:15 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 0:44 [PATCH 0/8] Support 64-bit U-Boot for Slim Bootloader aiden.park at intel.com
2020-04-22 0:45 ` [PATCH 1/8] x86: Add a new X86_RUN_64BIT_ONLY to Kconfig aiden.park at intel.com
2020-04-26 20:15 ` Simon Glass
2020-04-29 5:44 ` Park, Aiden
2020-04-30 9:13 ` Bin Meng
2020-05-01 18:36 ` Park, Aiden
2020-05-03 2:26 ` Simon Glass
2020-04-22 0:45 ` [PATCH 2/8] x86: start64: Add a hook at 64-bit entry aiden.park at intel.com
2020-04-26 20:15 ` Simon Glass
2020-04-29 5:48 ` Park, Aiden
2020-04-22 0:45 ` [PATCH 3/8] x86: start64: Support HOB in 64-bit U-Boot aiden.park at intel.com
2020-04-26 20:15 ` Simon Glass [this message]
2020-04-29 5:57 ` Park, Aiden
2020-04-22 0:45 ` [PATCH 4/8] x86: slimbootloader: Support 64-bit operation aiden.park at intel.com
2020-04-26 20:15 ` Simon Glass
2020-04-29 6:01 ` Park, Aiden
2020-04-29 18:03 ` Simon Glass
2020-05-01 18:34 ` Park, Aiden
2020-04-22 0:45 ` [PATCH 5/8] configs: slimbootloader: Add x86_64 slimbootloader config aiden.park at intel.com
2020-04-26 20:32 ` Simon Glass
2020-04-29 6:02 ` Park, Aiden
2020-04-30 9:13 ` Bin Meng
2020-04-22 0:45 ` [PATCH 6/8] x86: Fix 64-bit compile warning aiden.park at intel.com
2020-04-26 19:45 ` Simon Glass
2020-04-29 6:08 ` Park, Aiden
2020-04-22 0:45 ` [PATCH 7/8] x86: enable 64-bit kernel boot from 64-bit U-Boot aiden.park at intel.com
2020-04-26 20:15 ` Simon Glass
2020-04-29 6:17 ` Park, Aiden
2020-04-22 0:45 ` [PATCH 8/8] doc: slimbootloader: Update 64-bit build instruction aiden.park at intel.com
2020-04-30 9:13 ` Bin Meng
2020-04-26 20:15 ` [PATCH 0/8] Support 64-bit U-Boot for Slim Bootloader Simon Glass
2020-04-29 5:41 ` Park, Aiden
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=CAPnjgZ3LdMNzZP-QDfFT0GMfKbJYK_a38uW1RLAZQHw2NbS9hA@mail.gmail.com \
--to=sjg@chromium.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.