From: <rmandrad@gmail.com>
To: "'David Lechner'" <dlechner@baylibre.com>
Cc: <u-boot@lists.denx.de>, <trini@konsulko.com>,
<ryder.lee@mediatek.com>, <weijie.gao@mediatek.com>,
<chunfeng.yun@mediatek.com>,
<igor.belwon@mentallysanemainliners.org>, <jstephan@baylibre.com>,
<GSS_MTK_Uboot_upstream@mediatek.com>,
<emanuele.ghidoli@toradex.com>
Subject: RE: [PATCH] arm: mediatek: mt7988: restore full DRAM bank reporting
Date: Fri, 5 Jun 2026 14:08:33 +0100 [thread overview]
Message-ID: <003e01dcf4ec$6a507830$3ef16890$@gmail.com> (raw)
In-Reply-To: <CAMknhBFeV8qio29t1zNhoBNdumbWh2ErOE99dQEphDKZN8GodQ@mail.gmail.com>
Not the header file as TARGET_MT7988 sets SYS_CONFIG_NAME="mt7988" in arch/arm/mach-mediatek/Kconfig
In the mt7988 I don't see CFG_MAX_MEM_MAPPED used elsewhere than just in common/memsize.c where it limits get_effective_memsize()
Unsetting/removing CFG_MAX_MEM_MAPPED would take u-boot above 4gb... Some MediaTek ARM64 ports may keep U-Boot below 4 GiB because peripherals such as MMC need DMA buffers below 4 GiB ... so, it may work on my setup but not others. Also, not an expert on u-boot I would suggest for others to comment/review
-----Original Message-----
From: David Lechner <dlechner@baylibre.com>
Sent: 05 June 2026 13:52
To: Rudy Andram <rmandrad@gmail.com>
Cc: u-boot@lists.denx.de; trini@konsulko.com; ryder.lee@mediatek.com; weijie.gao@mediatek.com; chunfeng.yun@mediatek.com; igor.belwon@mentallysanemainliners.org; jstephan@baylibre.com; GSS_MTK_Uboot_upstream@mediatek.com; emanuele.ghidoli@toradex.com
Subject: Re: [PATCH] arm: mediatek: mt7988: restore full DRAM bank reporting
On Tue, Jun 2, 2026 at 6:24 PM Rudy Andram <rmandrad@gmail.com> wrote:
>
> MT7988 detects the full installed DRAM in dram_init(), but after
> commit bddd6bbef3dc ("arm: mediatek: mt7988: drop
> dram_init_banksize()") it fell back to the generic dram_init_banksize() implementation.
>
> That generic path populates bd->bi_dram[0].size with
> get_effective_memsize(), which is capped by CFG_MAX_MEM_MAPPED. On
> MT7988 this limits the exported DRAM bank to 3 GiB even when 8 GiB is
> installed.
Can we just remove the #define CFG_MAX_MEM_MAPPED (and the header file that contains it)? Or is it used somewhere else?
next prev parent reply other threads:[~2026-06-05 13:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 16:22 [PATCH] arm: mediatek: mt7988: restore full DRAM bank reporting Rudy Andram
2026-06-05 12:51 ` David Lechner
2026-06-05 13:08 ` rmandrad [this message]
2026-06-05 14:30 ` David Lechner
2026-06-05 14:48 ` David Lechner
2026-06-05 14:54 ` rmandrad
2026-06-05 15:00 ` David Lechner
2026-06-10 1:05 ` Weijie Gao
-- strict thread matches above, loose matches on Subject: below --
2026-05-30 5:37 Rudy Andram
2026-05-30 5:24 Rudy Andram
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='003e01dcf4ec$6a507830$3ef16890$@gmail.com' \
--to=rmandrad@gmail.com \
--cc=GSS_MTK_Uboot_upstream@mediatek.com \
--cc=chunfeng.yun@mediatek.com \
--cc=dlechner@baylibre.com \
--cc=emanuele.ghidoli@toradex.com \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=jstephan@baylibre.com \
--cc=ryder.lee@mediatek.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=weijie.gao@mediatek.com \
/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