All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: l-o <linux-omap@vger.kernel.org>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH RFC] OMAP2PLUS: Enable HIGHMEM
Date: Thu, 02 Jun 2011 18:51:15 +0530	[thread overview]
Message-ID: <4DE78E4B.7030009@ti.com> (raw)
In-Reply-To: <1307016381-21878-1-git-send-email-santosh.shilimkar@ti.com>

Fixing the change log ...

On 6/2/2011 5:36 PM, Santosh Shilimkar wrote:
> HIGMEM support is kernel is quite mature now and we have boards
HIGMEM support in kernel is quite mature now and we have boards
> like ZOOM, PANDA, SDP where 1 GB memories are installed.
>
> Enable HIGMEM to make use of the additional memory.
>
> Signed-off-by: Santosh Shilimkar<santosh.shilimkar@ti.com>
> ---
> This won't boards which doesn't have excess memory. Tested
This won't affect boards which doesn't have excess memory. Tested
> on OMAP4430 SDP
>
>   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 19d5891..25e819e 100644
> --- a/arch/arm/mach-omap2/Kconfig
> +++ b/arch/arm/mach-omap2/Kconfig
> @@ -19,6 +19,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
>


  reply	other threads:[~2011-06-02 13:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 12:06 [PATCH RFC] OMAP2PLUS: Enable HIGHMEM Santosh Shilimkar
2011-06-02 13:21 ` Santosh Shilimkar [this message]
2011-06-02 13:21 ` Premi, Sanjeev
2011-06-02 13:54   ` Santosh Shilimkar
2011-08-25  8:42 ` Santosh

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=4DE78E4B.7030009@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linux-omap@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.