From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH RFC] OMAP2PLUS: Enable HIGHMEM
Date: Thu, 02 Jun 2011 19:24:44 +0530 [thread overview]
Message-ID: <4DE79624.5080804@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB593024D2D2801@dbde02.ent.ti.com>
On 6/2/2011 6:51 PM, Premi, Sanjeev wrote:
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of
>> Shilimkar, Santosh
>> Sent: Thursday, June 02, 2011 5:36 PM
>> To: linux-omap@vger.kernel.org
>> Cc: Shilimkar, Santosh
>> Subject: [PATCH RFC] OMAP2PLUS: Enable HIGHMEM
>>
>> HIGMEM support is kernel is quite mature now and we have boards
> [sp] ^^ replace with "in"
yep. I sent that update in next email.
>
>> 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
>> on OMAP4430 SDP
>
> [sp] Comment is unclear on what happens on the boards with
> lesser memories esp. since the change will impact all
> boards. You may want to explain.
>
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.
>>
>> 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
>>
>> --
>> 1.6.0.4
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-02 13:54 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
2011-06-02 13:21 ` Premi, Sanjeev
2011-06-02 13:54 ` Santosh Shilimkar [this message]
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=4DE79624.5080804@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox