From: Andreas Schwab <schwab@linux-m68k.org>
To: Petr Tesarik <petrtesarik@huaweicloud.com>
Cc: linux-riscv@lists.infradead.org
Subject: Re: How to deal with openSBI reserved regions?
Date: Fri, 28 Jul 2023 12:52:42 +0200 [thread overview]
Message-ID: <874jlo9ukl.fsf@igel.home> (raw)
In-Reply-To: <76ff0f51-d6c1-580d-f943-061e93073306@huaweicloud.com> (Petr Tesarik's message of "Fri, 28 Jul 2023 12:02:49 +0200")
On Jul 28 2023, Petr Tesarik wrote:
> Or, is the provided DTB incorrect?
> Should the memory node exclude the firmware area?
It should be marked as reserved memory.
# ls /sys/firmware/devicetree/base/reserved-memory
#address-cells mmode_resv0@80040000/ name
#size-cells mmode_resv1@80000000/ ranges
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2023-07-28 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 10:02 How to deal with openSBI reserved regions? Petr Tesarik
2023-07-28 10:36 ` Alexandre Ghiti
2023-07-31 10:06 ` Petr Tesarik
2023-07-28 10:52 ` Andreas Schwab [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=874jlo9ukl.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-riscv@lists.infradead.org \
--cc=petrtesarik@huaweicloud.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox