From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] [U-boot]: Change FDT memory typpe from runtime data to acpi reclaim
Date: Thu, 11 Apr 2019 21:46:41 +0300 [thread overview]
Message-ID: <20190411184641.GA18297@apalos> (raw)
In-Reply-To: <CAKv+Gu_wVRXfJnzxzNn_NnYYoM1tDQb6g7_n+jfX9bAFUSKO5g@mail.gmail.com>
Hi Ard,
> On Thu, 11 Apr 2019 at 11:39, Ilias Apalodimas
> <ilias.apalodimas@linaro.org> wrote:
> >
> > Following Ard's suggestion:
> > Runtime data sections are intended for data that is used by the runtime
> > services implementations.
> > Let's change they type to EFI_ACPI_RECLAIM_MEMORY
> >
> > Suggested-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> > Signed-off-by: Ilias Apalodimas <ilias.apalodimas@linaro.org>
>
> It makes sense to mention that this actually fixes the boot issue you
> were seeing with the ARM Linux kernel when using short descriptors.
>
I mentioned that in the original mail thread as you were typing this mail.
Since i still think there *is* a kernel issue that should be fixed this just
'avoids' the problem. Not sure if it makes too much sense to include it here
Thanks
/Ilias
next prev parent reply other threads:[~2019-04-11 18:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-11 18:39 [U-Boot] [PATCH] [U-boot]: Change FDT memory typpe from runtime data to acpi reclaim Ilias Apalodimas
2019-04-11 18:43 ` Ard Biesheuvel
2019-04-11 18:46 ` Ilias Apalodimas [this message]
2019-04-11 19:34 ` Heinrich Schuchardt
2019-04-11 19:41 ` Ilias Apalodimas
2019-04-11 19:59 ` Heinrich Schuchardt
2019-04-11 20:50 ` Ard Biesheuvel
2019-04-12 17:16 ` Heinrich Schuchardt
2019-04-12 17:24 ` Ard Biesheuvel
2019-04-12 17:44 ` Heinrich Schuchardt
2019-04-12 17:47 ` Ard Biesheuvel
2019-04-12 17:36 ` Ilias Apalodimas
2019-04-12 17:49 ` Heinrich Schuchardt
2019-04-11 19:50 ` Ard Biesheuvel
2019-04-11 20:08 ` Heinrich Schuchardt
2019-04-11 20:44 ` Ard Biesheuvel
2019-04-12 19:24 ` Leif Lindholm
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=20190411184641.GA18297@apalos \
--to=ilias.apalodimas@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox