From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: John Crispin <blogic@openwrt.org>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH 1/7] MIPS: add detect_memory_region()
Date: Mon, 15 Apr 2013 15:26:39 +0400 [thread overview]
Message-ID: <516BE3EF.1020108@cogentembedded.com> (raw)
In-Reply-To: <1366022494-8355-1-git-send-email-blogic@openwrt.org>
Hello.
On 15-04-2013 14:41, John Crispin wrote:
> Add a generic way of detecting the available RAM. This function is based on the
> implementation already used by ath79.
> Signed-off-by: John Crispin <blogic@openwrt.org>
[...]
> diff --git a/arch/mips/kernel/setup.c b/arch/mips/kernel/setup.c
> index 4c774d5..dfe776a 100644
> --- a/arch/mips/kernel/setup.c
> +++ b/arch/mips/kernel/setup.c
[...]
> @@ -122,6 +123,25 @@ void __init add_memory_region(phys_t start, phys_t size, long type)
> boot_mem_map.nr_map++;
> }
>
> +void __init detect_memory_region(phys_t start, phys_t sz_min, phys_t sz_max)
Minor formatting nit: too many spaces after the last comma.
WBR, Sergei
prev parent reply other threads:[~2013-04-15 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 10:41 [PATCH 1/7] MIPS: add detect_memory_region() John Crispin
2013-04-15 10:41 ` [PATCH 2/7] MIPS: ralink: add memory definition to struct ralink_soc_info John Crispin
2013-04-15 10:41 ` [PATCH 3/7] MIPS: ralink: add memory definition for RT305x John Crispin
2013-04-15 11:29 ` Sergei Shtylyov
2013-04-15 10:41 ` [PATCH 4/7] MIPS: ralink: add memory definition for RT2880 John Crispin
2013-04-15 10:41 ` [PATCH 5/7] MIPS: ralink: add memory definition for RT3883 John Crispin
2013-04-15 10:41 ` [PATCH 6/7] MIPS: ralink: add memory definition for MT7620 John Crispin
2013-04-15 10:41 ` [PATCH 7/7] MIPS: ralink: make use of the new memory detection code John Crispin
2013-04-15 11:26 ` 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=516BE3EF.1020108@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=blogic@openwrt.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox