From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [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:37 UTC|newest]
Thread overview: 33+ 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:35 ` Lior Amsalem
2013-03-21 21:46 ` Jason Gunthorpe
2013-03-21 21:58 ` Lior Amsalem
2013-03-22 6:55 ` Arnd Bergmann
2013-03-21 21:41 ` Jason Gunthorpe
2013-03-21 22:26 ` Sebastian Hesselbarth
2013-03-22 9:55 ` Arnd Bergmann
2013-03-21 21:25 ` Andrew Lunn
2013-03-22 6:28 ` Andrew Lunn
2013-03-22 17:43 ` Jason Gunthorpe
2013-03-22 19:33 ` Arnd Bergmann
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=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).