linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: noodles@earth.li (Jonathan McDowell)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] pxa/vpac270: Enable SparseMEM for 256 MB of RAM
Date: Tue, 4 May 2010 21:55:50 +0100	[thread overview]
Message-ID: <20100504205550.GP3292@earth.li> (raw)
In-Reply-To: <1272992229-29361-1-git-send-email-marek.vasut@gmail.com>

On Tue, May 04, 2010 at 06:57:08PM +0200, Marek Vasut wrote:
> This patch enables SparseMEM for the Voipac PXA270 board. To work
> around the PHYS_OFFSET being set to 0xa0000000 and disallowing us to
> map the other partition at 0x80000000, the physical-to-virtual mapping
> of SDRAM was altered and the partition at 0x80000000 was moved to
> 0x10000000 in virtual memory (past the first SDRAM partition). As the
> Voipac PXA270 is probably the only PXA270 device which utilizes 256 MB
> of RAM, adding the following code into memory.h seems much less
> painful than tinkering with PHYS_OFFSET.
...
> +/*
> + * Voipac PXA270/PXA270M is probably the only board in the world with PXA27x
> + * that uses more than 128MB or SDRAM (256MB in the 'max configuration'). This

I think you mean "of SDRAM" here and the Balloon3 can be configured with
up to 512M (I'm pretty sure there were a few boards that had 768M on
them too, but I can't find any confirmation of that) and is a PXA270
board.

J.

-- 
Whatever the risk, NO one ever expects to get caught.

  parent reply	other threads:[~2010-05-04 20:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04 16:57 [PATCH 1/2] pxa/vpac270: Enable SparseMEM for 256 MB of RAM Marek Vasut
2010-05-04 16:57 ` [PATCH 2/2] pxa/vpac270: Add PMIC support Marek Vasut
2010-05-04 20:55 ` Jonathan McDowell [this message]
2010-05-04 21:06   ` [PATCH 1/2] pxa/vpac270: Enable SparseMEM for 256 MB of RAM Marek Vasut
2010-05-11 23:24 ` Marek Vasut

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=20100504205550.GP3292@earth.li \
    --to=noodles@earth.li \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).