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>,
Conor Dooley <conor@kernel.org>
Subject: [PATCH v3 3/3] riscv: configs: Add nommu PHONY defconfig for RV32
Date: Tue, 28 Feb 2023 19:26:57 -0500 [thread overview]
Message-ID: <20230301002657.352637-4-Mr.Bossman075@gmail.com> (raw)
In-Reply-To: <20230301002657.352637-1-Mr.Bossman075@gmail.com>
32bit risc-v can be configured to run without MMU. Introduce
rv32_nommu_virt_defconfig .PHONY target, that is based on
nommu_virt_defconfig. This is similar to how rv32_defconfig
is based on "defconfig".
Suggested-by: Conor Dooley <conor@kernel.org>
Signed-off-by: Jesse Taube <Mr.Bossman075@gmail.com>
Cc: Yimin Gu <ustcymgu@gmail.com>
---
V1->V2:
- Fix typo in commit title
V2->V3:
- Change from defconfig file to a PHONY config
---
arch/riscv/Makefile | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/riscv/Makefile b/arch/riscv/Makefile
index 6203c3378922..1b276f62f22b 100644
--- a/arch/riscv/Makefile
+++ b/arch/riscv/Makefile
@@ -174,3 +174,7 @@ rv64_randconfig:
PHONY += rv32_defconfig
rv32_defconfig:
$(Q)$(MAKE) -f $(srctree)/Makefile defconfig 32-bit.config
+
+PHONY += rv32_nommu_virt_defconfig
+rv32_nommu_virt_defconfig:
+ $(Q)$(MAKE) -f $(srctree)/Makefile nommu_virt_defconfig 32-bit.config
--
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 ` [PATCH v3 2/3] riscv: Kconfig: Allow RV32 to build with no MMU Jesse Taube
2023-03-01 1:22 ` Damien Le Moal
2023-03-01 0:26 ` Jesse Taube [this message]
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-4-Mr.Bossman075@gmail.com \
--to=mr.bossman075@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--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