From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH] ARM: OMAP2PLUS: Enable HIGHMEM
Date: Tue, 8 May 2012 16:59:27 -0700 [thread overview]
Message-ID: <20120508235926.GY5088@atomide.com> (raw)
In-Reply-To: <1335983327-14561-1-git-send-email-jon-hunter@ti.com>
* Jon Hunter <jon-hunter@ti.com> [120502 11:34]:
> From: Santosh Shilimkar <santosh.shilimkar@ti.com>
>
> HIGMEM support in kernel is quite mature now and we have boards
> like ZOOM, PANDA, SDP where 1 GB memories are installed. With
> HIGHMEM disabled not all of the 1GB of RAM (only ~700MB) can be
> accessed. Hence, enable HIGMEM to make use of the entire memory.
>
> On the boards which doesn't have more than 768 MB memory, all
> the memory is directly mapped in "lowmem" and highmem isn't
> exercised. Hence, there should be no impact by enabling HIGHMEM
> for boards that do not need it.
>
> Tested on OMAP4460 Panda-ES.
>
> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> Tested-by: Jon Hunter <jon-hunter@ti.com>
> ---
> arch/arm/mach-omap2/Kconfig | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/Kconfig b/arch/arm/mach-omap2/Kconfig
> index 8141b76..964ee67 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -17,6 +17,7 @@ config ARCH_OMAP2PLUS_TYPICAL
> select MENELAUS if ARCH_OMAP2
> select TWL4030_CORE if ARCH_OMAP3 || ARCH_OMAP4
> select TWL4030_POWER if ARCH_OMAP3 || ARCH_OMAP4
> + select HIGHMEM
> help
> Compile a kernel suitable for booting most boards
Thanks applying into board branch.
Regards,
Tony
prev parent reply other threads:[~2012-05-08 23:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 18:28 [PATCH] ARM: OMAP2PLUS: Enable HIGHMEM Jon Hunter
2012-05-08 23:59 ` Tony Lindgren [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=20120508235926.GY5088@atomide.com \
--to=tony@atomide.com \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=santosh.shilimkar@ti.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 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.