From: Andreas Schwab <schwab@suse.de>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Minda Chen <minda.chen@starfivetech.com>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Rick Chen <rick@andestech.com>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Hal Feng <hal.feng@starfivetech.com>,
Tom Rini <trini@konsulko.com>,
Chanho Park <chanho61.park@samsung.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Nam Cao <namcao@linutronix.de>,
Jaehoon Chung <jh80.chung@samsung.com>,
E Shattow <lucent@gmail.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 0/2] configs: JH7110: enable EFI_LOADER_BOUNCE_BUFFER
Date: Thu, 21 Nov 2024 16:24:55 +0100 [thread overview]
Message-ID: <mvmjzcwobi0.fsf@suse.de> (raw)
In-Reply-To: <20241121142522.59059-1-heinrich.schuchardt@canonical.com> (Heinrich Schuchardt's message of "Thu, 21 Nov 2024 15:25:20 +0100")
On Nov 21 2024, Heinrich Schuchardt wrote:
> Our MMC driver for JH7110 boards only supports reading to the low 4 GiB of
> memory. Booting boards with more memory requires EFI_LOADER_BOUNCE_BUFFER.
That doesn't change the situation with the booting problem I have.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2024-11-21 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 14:25 [PATCH 0/2] configs: JH7110: enable EFI_LOADER_BOUNCE_BUFFER Heinrich Schuchardt
2024-11-21 14:25 ` [PATCH 1/2] efi_loader: allow EFI_LOADER_BOUNCE_BUFFER on all architectures Heinrich Schuchardt
2024-11-21 14:25 ` [PATCH 2/2] configs: JH7110: enable EFI_LOADER_BOUNCE_BUFFER Heinrich Schuchardt
2024-11-21 15:24 ` Andreas Schwab [this message]
2024-11-21 16:05 ` [PATCH 0/2] " Heinrich Schuchardt
2024-11-21 22:41 ` E Shattow
2024-11-22 6:32 ` Sughosh Ganu
2024-11-22 8:25 ` E Shattow
2024-11-22 14:33 ` Loic Devulder
2024-11-26 6:32 ` E Shattow
2024-11-26 10:32 ` E Shattow
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=mvmjzcwobi0.fsf@suse.de \
--to=schwab@suse.de \
--cc=aurelien@aurel32.net \
--cc=chanho61.park@samsung.com \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=ilias.apalodimas@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=lucent@gmail.com \
--cc=minda.chen@starfivetech.com \
--cc=namcao@linutronix.de \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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.