linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben-linux@fluff.org (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] s5pv210: Change the base ram address to 0x3000'0000
Date: Fri, 28 May 2010 05:20:29 +0100	[thread overview]
Message-ID: <20100528042029.GS4720@trinity.fluff.org> (raw)
In-Reply-To: <AANLkTikfCdHgzgRjVikeGYg5wK_meh3NyDRCOzs6j6uc@mail.gmail.com>

On Fri, May 28, 2010 at 01:02:24PM +0900, Kyungmin Park wrote:
> On Fri, May 28, 2010 at 12:53 PM, Ben Dooks <ben-linux@fluff.org> wrote:
> > On Fri, May 28, 2010 at 11:35:59AM +0900, Kyungmin Park wrote:
> >> s5pc110 (aka s5pv210) has 2 DRAM port and used it both usually.
> >> Assume DMC0 starts with 0x2000'0000 with 128MiB.
> >> DMC1 starts with 0x4000'0000 with 128MiB.
> >> Note that DMC1 has to start address 0x4000'0000 at least.
> >>
> >> Then there's too much memory hole 0x1800'0000 (128MiB + 256MiB)
> >>
> >> To reduce memory waste, the DMC0 start with 0x3000'0000.

but you just said DMC0 starts at 0x2... ? Is this reconfigurable via
software, if so can it be moved once initialisation si done? how fixed
is this?
 
> Hi,
> 
> >
> > We should be using SPARSEMEM now, is it not reducing any wastage
> > in virtual memory space?
> 
> Please consider the older kernel also. and most systems are designed
> for 0x3000'0000.

Ok, will a kernel with the base-address set to 0x3... work when loaded
on a system with RAM starting at 0x2... ? I'm not sure the answer to this
question.

I'd rather try and get one kernel working on all systems with the S5PV210
if possible instead of havign to pick which ones have certain base addresses


> >
> > How will the user change their board to deal with this change to hte
> > kernel?
> 
> Now we got the these memory
> DMC0 has 128MiB and DMC1 has 512MiB.
> Then it uses the memory from 0x2000'0000 to 0x5fff'ffff. it used 1GiB
> memory address space.
> Of course we can enable thie HIGHMEM but older kernel doesn't support it fully.
> Also I hope to use the 3G/1G memory scheme.

Given you can only get 1G of real memory into a S5PV210, is it really
necessary to go to 3G/1G? What problems are there with 2/2 split?

> How to you think?

I thought that when the s5pv210 was submitted we enabled the SPARSMEM
support so that whatever DRAM configuration we could handle it within
a single kernel.

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.

  reply	other threads:[~2010-05-28  4:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-28  2:35 [PATCH] s5pv210: Change the base ram address to 0x3000'0000 Kyungmin Park
2010-05-28  3:53 ` Ben Dooks
2010-05-28  4:02   ` Kyungmin Park
2010-05-28  4:20     ` Ben Dooks [this message]
2010-05-28  5:25       ` Kyungmin Park
2010-05-28  6:02         ` Ben Dooks
2010-05-28  6:19           ` Kyungmin Park
2010-05-28  7:09             ` Ben Dooks
2010-05-28 14:17               ` Kyungmin Park
2010-05-31  0:18 ` Kukjin Kim
2010-05-31  0:39 ` Ben Dooks
2010-05-31  0:47   ` Kyungmin Park
2010-05-31  0:56     ` Kyungmin Park

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=20100528042029.GS4720@trinity.fluff.org \
    --to=ben-linux@fluff.org \
    --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).