From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: Include all 2 GiB of memory on APE6EVM
Date: Wed, 10 Apr 2013 02:09:37 +0000 [thread overview]
Message-ID: <20130410020936.GI11105@verge.net.au> (raw)
In-Reply-To: <CANqRtoSvoyCDGMtLof68y2q1feiEtE=HXMi1=sTi-rOKexAuhQ@mail.gmail.com>
On Wed, Apr 10, 2013 at 10:38:49AM +0900, Magnus Damm wrote:
> Hi Simon, Arnd,
>
> On Wed, Apr 10, 2013 at 9:35 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Wed, Apr 10, 2013 at 07:27:41AM +0900, Magnus Damm wrote:
> >> Hi Simon,
> >>
> >> On Wed, Apr 10, 2013 at 1:14 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > On Tue, Apr 09, 2013 at 09:34:34PM +0900, Simon Horman wrote:
> >> >> On Mon, Apr 08, 2013 at 10:44:44AM +0900, Magnus Damm wrote:
> >> >> > From: Takashi Yoshii <takashi.yoshii.zj@renesas.com>
> >> >> >
> >> >> > Add 1GiB of DRAM at 0x2_0000_0000
> >> >> >
> >> >> > Signed-off-by: Takashi Yoshii <takashi.yoshii.zj@renesas.com>
> >> >> > Signed-off-by: Magnus Damm <damm@opensource.se>
> >> >>
> >> >> Thanks, queued up in the boards-ape6evm branch.
> >> >
> >> > I have dropped this patch as it appears to prevent
> >> > the board from booting.
> >>
> >> Is it possible that LPAE=n and HIGHMEM=y in your particular kernel
> >> configuration?
> >
> > Yes, I have confirmed that is what using the ape6evm_defconfig results in.
oup >
> >> >From what I can tell HIGHMEM is broken in cases of large amounts of
> >> memory. Try disabling that as a short-term workaround. Then of course
> >> someone needs to track down why the generic code doesn't work as
> >> expected.
> >
> > I have confirmed that disabling HIGHMEM allows the board to boot
> > with this patch applied.
>
> Thanks for checking.
>
> So HIGHMEM without LPAE seems busted on boards using more than 32-bits
> for memory.
>
> I'd like to help out fixing this issue, but I'd like to make sure that
> no one else is working on this.
>
> Arnd, are you aware on any work related to making HIGHMEM work without LPAE?
>
> > Should I prepare a patch to the defconfig to accompany this patch?
>
> I believe that would affect a bunch of boards so I don't think that is
> necessary at this point. Thanks anyway.
>
> Would it be possible for you to queue up this change in a APE6EVM topic branch?
Sure, I have pushed topic/ape6evm-2gb.
I also plan to push topic/ape6evm-2gb+renesas-next-20130410v2
once I have finalised renesas-next-20130410v2.
next prev parent reply other threads:[~2013-04-10 2:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 1:44 [PATCH] ARM: shmobile: Include all 2 GiB of memory on APE6EVM Magnus Damm
2013-04-09 12:34 ` Simon Horman
2013-04-09 16:14 ` Simon Horman
2013-04-09 22:27 ` Magnus Damm
2013-04-10 0:35 ` Simon Horman
2013-04-10 1:38 ` Magnus Damm
2013-04-10 2:09 ` Simon Horman [this message]
2013-10-31 3:15 ` Magnus Damm
2013-10-31 4:20 ` Simon Horman
2013-10-31 8:02 ` Magnus Damm
2013-11-06 1:48 ` Simon Horman
2013-11-06 9:48 ` Magnus Damm
2013-11-08 6:26 ` Simon Horman
2013-11-25 2:47 ` Simon Horman
2013-11-28 7:56 ` Simon Horman
2013-10-31 3:18 ` [PATCH] ARM: shmobile: Include all 2 GiB of memory on APE6EVM DT Ref Magnus Damm
2013-11-28 7:55 ` Simon Horman
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=20130410020936.GI11105@verge.net.au \
--to=horms@verge.net.au \
--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).