From: Tom Rini <trini@konsulko.com>
To: "Pali Rohár" <pali@kernel.org>
Cc: Simon Glass <sjg@chromium.org>,
Sean Anderson <sean.anderson@seco.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH v2] board_f: show_dram_config: Print also real DRAM size
Date: Fri, 23 Sep 2022 18:48:49 -0400 [thread overview]
Message-ID: <20220923224849.GR3044094@bill-the-cat> (raw)
In-Reply-To: <20220918112328.4570-1-pali@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Sun, Sep 18, 2022 at 01:23:27PM +0200, Pali Rohár wrote:
> 32-bit U-Boot builds cannot use more than around 2 GB of DDR memory. But on
> some platforms/boards it is possible to connect also 4 GB SODIMM DDR memory.
> U-Boot currently prints only effective size of RAM which can use, which may
> be misleading as somebody would expect that this line prints total size of
> connected DDR modules. So change show_dram_config code to prints both real
> and effective DRAM size if they are different. If they are same then print
> just one number like before. It is possible that effective size is just few
> bytes smaller than the real size, so print both numbers only in case
> function print_size() prints formats them differently.
>
> Signed-off-by: Pali Rohár <pali@kernel.org>
Applied to u-boot/next, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2022-09-23 22:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 9:39 [PATCH] board_f: show_dram_config: Print also real DRAM size Pali Rohár
2022-09-12 13:34 ` Simon Glass
2022-09-12 18:56 ` Pali Rohár
2022-09-12 21:58 ` Sean Anderson
2022-09-14 17:10 ` Simon Glass
2022-09-14 17:32 ` Pali Rohár
2022-09-14 18:31 ` Simon Glass
2022-09-18 11:30 ` Pali Rohár
2022-09-19 21:10 ` Simon Glass
2022-09-18 11:23 ` [PATCH v2] " Pali Rohár
2022-09-23 22:48 ` Tom Rini [this message]
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=20220923224849.GR3044094@bill-the-cat \
--to=trini@konsulko.com \
--cc=pali@kernel.org \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--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