From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Cc: George McCollister <george.mccollister@gmail.com>
Subject: [PATCH 5/5] x86: som-db5800-som-6867: Adjust CONFIG_TEXT_BASE
Date: Thu, 24 Nov 2022 19:33:29 +0800 [thread overview]
Message-ID: <20221124113329.3162008-5-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20221124113329.3162008-1-bmeng.cn@gmail.com>
At present U-Boot no longer builds as a complete rom for som-db5800-som-6867.
BINMAN .binman_stamp
Wrote map file './rom.map' to show errors
binman: Section '/binman/rom': contents size 0x80302c (8400940) exceeds section size 0x800000 (8388608)
Checking rom.map we see 'intel-vga' section is overlapped with
other sections:
<none> fff00000 0009f7c8 u-boot-with-ucode-ptr
<none> fff90000 00010000 intel-vga
<none> fff9f7c8 00001aae u-boot-dtb-with-ucode
Let's adjust CONFIG_TEXT_BASE to allow more space for U-Boot codes.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
---
configs/som-db5800-som-6867_defconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/som-db5800-som-6867_defconfig b/configs/som-db5800-som-6867_defconfig
index 5d401e6c2d..f6b2109e2b 100644
--- a/configs/som-db5800-som-6867_defconfig
+++ b/configs/som-db5800-som-6867_defconfig
@@ -1,5 +1,5 @@
CONFIG_X86=y
-CONFIG_TEXT_BASE=0xFFF00000
+CONFIG_TEXT_BASE=0xFFE00000
CONFIG_NR_DRAM_BANKS=8
CONFIG_ENV_SIZE=0x1000
CONFIG_ENV_OFFSET=0x6EF000
--
2.34.1
next prev parent reply other threads:[~2022-11-24 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 11:33 [PATCH 1/5] x86: bayleybay: Adjust CONFIG_TEXT_BASE Bin Meng
2022-11-24 11:33 ` [PATCH 2/5] x86: minnowmax: " Bin Meng
2022-11-26 2:46 ` Simon Glass
2022-11-26 7:43 ` Bin Meng
2022-11-27 14:35 ` Simon Glass
2022-11-24 11:33 ` [PATCH 3/5] x86: conga-qeval20-qa3-e3845: " Bin Meng
2022-11-24 11:33 ` [PATCH 4/5] x86: dfi-bt700: " Bin Meng
2022-11-25 6:03 ` Stefan Roese
2022-11-24 11:33 ` Bin Meng [this message]
2022-12-14 3:51 ` [PATCH 1/5] x86: bayleybay: " Bin Meng
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=20221124113329.3162008-5-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=u-boot@lists.denx.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