From: Sander Vanheule <sander@svanheule.net>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
Sander Vanheule <sander@svanheule.net>,
Olliver Schinagl <oliver@schinagl.nl>
Subject: [PATCH] mips: Realtek RTL: select NO_EXCEPT_FILL
Date: Sun, 15 Jan 2023 13:19:22 +0100 [thread overview]
Message-ID: <20230115121922.6359-1-sander@svanheule.net> (raw)
The CPUs in these SoCs support MIPS32 R2, and allow ebase relocation.
Even if the default exception base of 0x80000000 is used, the
MIPS_GENERIC load address of 0x80100000 leaves sufficient space to not
need an extra 0x400 bytes of padding.
Suggested-by: Olliver Schinagl <oliver@schinagl.nl>
Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
Olliver has suggested to make this change, in order to reduce the delta
with a fully generic MIPS kernel.
I hope the patch description makes sense, as I based the argumentation
on the behaviour of the code, and similar commits 7d6d28377783 ("MIPS:
Loongson64: select NO_EXCEPT_FILL") and dd54dedd947d ("MIPS: BCM47XX:
select NO_EXCEPT_FILL"). The change was tested on an RTL8380 and an
RTL8393 device, where it appears to work as expected.
Best,
Sander
arch/mips/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
index 2db5c853992e..a8895aaa490e 100644
--- a/arch/mips/Kconfig
+++ b/arch/mips/Kconfig
@@ -627,6 +627,7 @@ config MACH_REALTEK_RTL
select IRQ_MIPS_CPU
select CEVT_R4K
select CSRC_R4K
+ select NO_EXCEPT_FILL
select SYS_HAS_CPU_MIPS32_R1
select SYS_HAS_CPU_MIPS32_R2
select SYS_SUPPORTS_32BIT_KERNEL
--
2.39.0
next reply other threads:[~2023-01-15 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 12:19 Sander Vanheule [this message]
2023-01-27 16:27 ` [PATCH] mips: Realtek RTL: select NO_EXCEPT_FILL Thomas Bogendoerfer
2023-01-28 14:39 ` Olliver Schinagl
2023-02-05 16:19 ` Thomas Bogendoerfer
2023-02-05 18:33 ` Olliver Schinagl
2023-02-17 17:37 ` Thomas Bogendoerfer
2023-02-17 19:27 ` Olliver Schinagl
2023-02-19 9:02 ` Thomas Bogendoerfer
2023-02-19 9:27 ` Olliver Schinagl
2023-02-19 10:31 ` Thomas Bogendoerfer
2023-02-19 16:07 ` Olliver Schinagl
2023-02-22 15:23 ` Olliver Schinagl
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=20230115121922.6359-1-sander@svanheule.net \
--to=sander@svanheule.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=oliver@schinagl.nl \
--cc=tsbogend@alpha.franken.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