From: Andrew Lunn <andrew@lunn.ch>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory CLEMENT <gregory.clement@free-electrons.com>,
Jason Cooper <jason@lakedaemon.net>,
Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Olof Johansson <olof@lixom.net>, Nicolas Pitre <nico@fluxnic.net>,
Lior Amsalem <alior@marvell.com>,
Maen Suleiman <maen@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
Shadi Ammouri <shadi@marvell.com>,
Eran Ben-Avi <benavi@marvell.com>,
Yehuda Yitschak <yehuday@marvell.com>,
Nadav Haklai <nadavh@marvell.com>,
Ike Pan <ike.pan@canonical.com>,
Chris Van Hoof <vanhoof@canonical.com>,
Dan Frazier <dann.frazier@canonical.com>,
Leif Lindholm <leif.lindholm@arm.com>,
Jon Masters <jcm@redhat.com>, David Marlin <dmarlin@redhat.com>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits
Date: Thu, 21 Mar 2013 21:37:51 +0100 [thread overview]
Message-ID: <20130321203751.GP21478@lunn.ch> (raw)
In-Reply-To: <20130321212236.1015295d@skate>
On Thu, Mar 21, 2013 at 09:22:36PM +0100, Thomas Petazzoni wrote:
> Dear Andrew Lunn,
>
> On Thu, 21 Mar 2013 21:15:33 +0100, Andrew Lunn wrote:
>
> > Could you recommend a document which introduces LPAE.
> >
> > Only being able to address 7GB seems a bit odd to me. I kind of
> > expected you set up the translation tables to map a page in the 32 bit
> > address range to any arbitrary page in the 40 bit address range. So
> > leaving 0xC0000000 to 0xffffffff in the 32bit address range clear is
> > easy. But why do you loose space in the 40bit address range?
>
> translation tables convert virtual addresses to physical addresses.
> Here, we are only talking about physical addresses. There is an overlap
> between the physical addresses used by the RAM, and the physical
> addresses at which I/O devices are visible.
>
> And I'm not sure the SDRAM address decoding windows allows to split the
> first 4 GB of RAM into two areas, one that would be mapped starting at
> physical address 0x0, and another area that would be mapped at a
> different address (above 4 GB).
So why not map the whole SDRAM above 4GB physical address?
Thanks
Andrew
next prev parent reply other threads:[~2013-03-21 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 16:26 [PATCH 0/5] arm: mvebu: Enable LPAE support for Armada XP SoCs Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 1/5] arm: mvebu: Aligne the internal registers virtual base to support LPAE Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 2/5] arm: mvebu: Select DMA_BOUNCE when LPAE is selected in Kconfig Gregory CLEMENT
2013-03-21 18:19 ` Rob Herring
2013-03-21 19:18 ` Andrew Lunn
2013-03-22 11:32 ` Russell King - ARM Linux
2013-03-21 16:26 ` [PATCH 3/5] arm: mvebu: Enable pj4b on LPAE compilations Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 4/5] arm: dts: Add a 64 bits version of the skeleton device tree Gregory CLEMENT
2013-03-21 16:26 ` [PATCH 5/5] arm: dts: Convert mvebu device tree files to 64 bits Gregory CLEMENT
2013-03-21 17:59 ` Rob Herring
2013-03-21 19:03 ` Arnd Bergmann
2013-03-21 19:18 ` Thomas Petazzoni
2013-03-21 21:31 ` Arnd Bergmann
2013-03-21 22:30 ` Sebastian Hesselbarth
2013-03-21 20:15 ` Andrew Lunn
2013-03-21 20:22 ` Thomas Petazzoni
2013-03-21 20:30 ` Jason Cooper
2013-03-21 20:37 ` Andrew Lunn [this message]
2013-03-21 21:08 ` Thomas Petazzoni
2013-03-21 21:16 ` Thomas Petazzoni
2013-03-21 20:55 ` Jason Gunthorpe
2013-03-21 21:15 ` Thomas Petazzoni
2013-03-21 21:41 ` Jason Gunthorpe
2013-03-21 22:26 ` Sebastian Hesselbarth
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=20130321203751.GP21478@lunn.ch \
--to=andrew@lunn.ch \
--cc=alior@marvell.com \
--cc=arnd@arndb.de \
--cc=benavi@marvell.com \
--cc=dann.frazier@canonical.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dmarlin@redhat.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=gregory.clement@free-electrons.com \
--cc=ike.pan@canonical.com \
--cc=jason@lakedaemon.net \
--cc=jcm@redhat.com \
--cc=leif.lindholm@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maen@marvell.com \
--cc=nadavh@marvell.com \
--cc=nico@fluxnic.net \
--cc=olof@lixom.net \
--cc=rob.herring@calxeda.com \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shadi@marvell.com \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=vanhoof@canonical.com \
--cc=yehuday@marvell.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