U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bin Meng <bmeng.cn@gmail.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/5] x86: bayleybay: Adjust CONFIG_TEXT_BASE
Date: Thu, 24 Nov 2022 19:33:25 +0800	[thread overview]
Message-ID: <20221124113329.3162008-1-bmeng.cn@gmail.com> (raw)

At present U-Boot no longer builds as a complete rom for bayleybay.

    BINMAN  .binman_stamp
  Wrote map file './rom.map' to show errors
  binman: Section '/binman/rom': contents size 0x814706 (8472326) exceeds section size 0x800000 (8388608)

Checking rom.map we see 'fdtmap' section is overlapped with
'intel-vga' and 'intel-fsp' sections:

  <none>     fffa2150  0002a000  u-boot-ucode
  <none>     fffb0000  00010000  intel-vga
  <none>     fffc0000  00038000  intel-fsp
  <none>     fffcc150  00000539  fdtmap

Let's adjust CONFIG_TEXT_BASE to allow more space for U-Boot codes.

Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
---

 configs/bayleybay_defconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configs/bayleybay_defconfig b/configs/bayleybay_defconfig
index 5f43f4c0ee..3556fe6b12 100644
--- a/configs/bayleybay_defconfig
+++ b/configs/bayleybay_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=0x6FF000
-- 
2.34.1


             reply	other threads:[~2022-11-24 11:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 11:33 Bin Meng [this message]
2022-11-24 11:33 ` [PATCH 2/5] x86: minnowmax: Adjust CONFIG_TEXT_BASE 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 ` [PATCH 5/5] x86: som-db5800-som-6867: " Bin Meng
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-1-bmeng.cn@gmail.com \
    --to=bmeng.cn@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