From: Tobias Waldekranz <tobias@waldekranz.com>
To: barebox@lists.infradead.org
Subject: [PATCH v2 5/7] MIPS: qemu-malta_defconfig: Use largest possible relocation table
Date: Tue, 9 Sep 2025 15:18:38 +0200 [thread overview]
Message-ID: <20250909131843.2260573-6-tobias@waldekranz.com> (raw)
In-Reply-To: <20250909131843.2260573-1-tobias@waldekranz.com>
With the upcoming device-mapper selftest, enabling CONFIG_DISK and
CONFIG_DM_BLK pushed the resulting relocation table over the 0x8000
default.
Given that the target hardware is QEMU, RAM is unlikely to be a scarce
resource. Therefore, go for the maximum allowed to avoid being back
here again when the next thing is added.
Signed-off-by: Tobias Waldekranz <tobias@waldekranz.com>
---
arch/mips/configs/qemu-malta_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/mips/configs/qemu-malta_defconfig b/arch/mips/configs/qemu-malta_defconfig
index 5f2b4470b8..e5bc8ff8cb 100644
--- a/arch/mips/configs/qemu-malta_defconfig
+++ b/arch/mips/configs/qemu-malta_defconfig
@@ -1,3 +1,4 @@
+CONFIG_MIPS_RELOCATION_TABLE_SIZE=0x10000
CONFIG_BOARD_QEMU_MALTA=y
CONFIG_IMAGE_COMPRESSION_XZKERN=y
CONFIG_NAME="qemu-malta_defconfig"
--
2.43.0
next prev parent reply other threads:[~2025-09-09 16:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:18 [PATCH v2 0/7] dm: Initial work on a device mapper Tobias Waldekranz
2025-09-09 13:18 ` [PATCH v2 1/7] string: add strtok/strtokv Tobias Waldekranz
2025-09-09 13:18 ` [PATCH v2 2/7] vsprintf: Add rasprintf(): the reallocing string printf family Tobias Waldekranz
2025-09-09 13:18 ` [PATCH v2 3/7] dm: Add initial device mapper infrastructure Tobias Waldekranz
2025-09-09 13:18 ` [PATCH v2 4/7] dm: linear: Add linear target Tobias Waldekranz
2025-09-09 13:18 ` Tobias Waldekranz [this message]
2025-09-09 13:18 ` [PATCH v2 6/7] test: self: dm: Add test of " Tobias Waldekranz
2025-09-09 13:18 ` [PATCH v2 7/7] commands: dmsetup: Basic command set for dm device management Tobias Waldekranz
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=20250909131843.2260573-6-tobias@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=barebox@lists.infradead.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