From: Jesse Taube <mr.bossman075@gmail.com>
To: linux-riscv@lists.infradead.org
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Jesse Taube <Mr.Bossman075@gmail.com>,
Yimin Gu <ustcymgu@gmail.com>,
Damien Le Moal <damien.lemoal@wdc.com>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Waldemar Brodkorb <wbx@openadk.org>,
Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: [PATCH v3 2/3] riscv: Kconfig: Allow RV32 to build with no MMU
Date: Tue, 28 Feb 2023 19:26:56 -0500 [thread overview]
Message-ID: <20230301002657.352637-3-Mr.Bossman075@gmail.com> (raw)
In-Reply-To: <20230301002657.352637-1-Mr.Bossman075@gmail.com>
From: Yimin Gu <ustcymgu@gmail.com>
Some RISC-V 32bit cores do not have an MMU, and the kernel should be
able to build for them. This patch enables the RV32 to be built with
no MMU support.
Signed-off-by: Yimin Gu <ustcymgu@gmail.com>
CC: Jesse Taube <Mr.Bossman075@gmail.com>
Tested-by: Waldemar Brodkorb <wbx@openadk.org>
Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
---
V1->V2:
- Fix typo in commit description
V2->V3:
- No change
---
arch/riscv/Kconfig | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index c5e42cc37604..d1f661425790 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -177,8 +177,8 @@ config MMU
config PAGE_OFFSET
hex
- default 0xC0000000 if 32BIT
- default 0x80000000 if 64BIT && !MMU
+ default 0xC0000000 if 32BIT && MMU
+ default 0x80000000 if !MMU
default 0xff60000000000000 if 64BIT
config KASAN_SHADOW_OFFSET
@@ -279,7 +279,6 @@ config ARCH_RV32I
select GENERIC_LIB_ASHRDI3
select GENERIC_LIB_LSHRDI3
select GENERIC_LIB_UCMPDI2
- select MMU
config ARCH_RV64I
bool "RV64I"
--
2.39.0
next prev parent reply other threads:[~2023-03-01 0:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:26 [PATCH v3 0/3] Add RISC-V 32 NOMMU support Jesse Taube
2023-03-01 0:26 ` [PATCH v3 1/3] clk: k210: remove an implicit 64-bit division Jesse Taube
2023-03-01 1:19 ` Damien Le Moal
2023-03-06 22:31 ` Stephen Boyd
2023-03-06 22:35 ` Conor Dooley
2023-03-06 22:37 ` Stephen Boyd
2023-03-06 22:41 ` Stephen Boyd
2023-03-06 22:48 ` Palmer Dabbelt
2023-03-01 0:26 ` Jesse Taube [this message]
2023-03-01 1:22 ` [PATCH v3 2/3] riscv: Kconfig: Allow RV32 to build with no MMU Damien Le Moal
2023-03-01 0:26 ` [PATCH v3 3/3] riscv: configs: Add nommu PHONY defconfig for RV32 Jesse Taube
2023-03-01 4:07 ` [PATCH v3 0/3] Add RISC-V 32 NOMMU support Randy Dunlap
2023-03-01 4:42 ` Damien Le Moal
2023-03-08 1:26 ` Jesse Taube
[not found] ` <62852ee1-3763-3323-c3a8-f1e84f70204a@infradead.org>
2023-03-08 2:30 ` Jesse Taube
2023-03-08 2:33 ` Randy Dunlap
2023-03-08 2:51 ` Randy Dunlap
2023-03-08 2:54 ` Jesse Taube
2023-03-08 3:23 ` Randy Dunlap
2023-03-08 3:42 ` Damien Le Moal
2023-03-08 3:46 ` Jesse Taube
2023-03-08 4:11 ` Damien Le Moal
2023-03-14 18:35 ` Jesse Taube
2023-03-14 19:16 ` Conor Dooley
2023-03-08 3:51 ` Randy Dunlap
2023-03-25 11:57 ` Conor Dooley
2023-03-28 18:50 ` (subset) " Palmer Dabbelt
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=20230301002657.352637-3-Mr.Bossman075@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=damien.lemoal@wdc.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=sboyd@kernel.org \
--cc=ustcymgu@gmail.com \
--cc=wbx@openadk.org \
/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