All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Markos Chandras <markos.chandras@imgtec.com>, linux-mips@linux-mips.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] MIPS: Malta: malta-memory: Detect and fix bad memsize values
Date: Fri, 27 Feb 2015 15:34:44 +0300	[thread overview]
Message-ID: <54F06464.9040307@cogentembedded.com> (raw)
In-Reply-To: <1425023492-23248-1-git-send-email-markos.chandras@imgtec.com>

Hello.

On 2/27/2015 10:51 AM, Markos Chandras wrote:

> memsize denotes the amount of RAM we can access from kseg{0,1} and
> that should be up to 256M. In case the bootloader reports a value
> higher than that (perhaps reporting all the available RAM) it's best
> if we fix it ourselves and just warn the user about that. This is
> usually a problem with the bootloader and/or its environment.

> Cc: <stable@vger.kernel.org> # v3.15+
> Signed-off-by: Markos Chandras <markos.chandras@imgtec.com>
> ---
>   arch/mips/mti-malta/malta-memory.c | 5 +++++
>   1 file changed, 5 insertions(+)

> diff --git a/arch/mips/mti-malta/malta-memory.c b/arch/mips/mti-malta/malta-memory.c
> index 8fddd2cdbff7..3a0a06450ef8 100644
> --- a/arch/mips/mti-malta/malta-memory.c
> +++ b/arch/mips/mti-malta/malta-memory.c
> @@ -53,6 +53,11 @@ fw_memblock_t * __init fw_getmdesc(int eva)
>   		pr_warn("memsize not set in YAMON, set to default (32Mb)\n");
>   		physical_memsize = 0x02000000;
>   	} else {
> +		if (memsize > (256 << 20)) { /* memsize should be capped to 256M */
> +			pr_warn("Unsupported memsize value (0x%lx) detected! Using 0x10000000 (256M) instead\n",
> +				memsize);
> +			memsize = (256 << 20);

    () not needed here.

[...]

WBR, Sergei

      reply	other threads:[~2015-02-27 12:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27  7:51 [PATCH] MIPS: Malta: malta-memory: Detect and fix bad memsize values Markos Chandras
2015-02-27  7:51 ` Markos Chandras
2015-02-27 12:34 ` Sergei Shtylyov [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=54F06464.9040307@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=linux-mips@linux-mips.org \
    --cc=markos.chandras@imgtec.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.