All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Liviu Dudau <liviu.dudau@foss.arm.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	Peter Hoyes <peter.hoyes@arm.com>, Simon Glass <sjg@chromium.org>,
	u-boot@lists.denx.de, Sean Anderson <sean.anderson@seco.com>
Subject: Re: [PATCH 09/11] vexpress64: generalise page table generation
Date: Sat, 2 Apr 2022 20:14:26 -0400	[thread overview]
Message-ID: <20220403001426.GJ14476@bill-the-cat> (raw)
In-Reply-To: <20220304163018.3167841-10-andre.przywara@arm.com>

[-- Attachment #1: Type: text/plain, Size: 877 bytes --]

On Fri, Mar 04, 2022 at 04:30:16PM +0000, Andre Przywara wrote:

> In preparation for the ARMv8-R64 FVP support, which has DRAM mapped at
> 0x0, generalise the page table generation, by using symbolic names for
> the address ranges instead of fixed numbers.
> 
> We already define the base of the DRAM and MMIO regions, so just use
> those symbols in the page table description. Rename V2M_BASE to the more
> speaking V2M_DRAM_BASE on the way.
> 
> On the VExpress memory map, the address space right after 4GB is of no
> particular interest to software, as the whole of DRAM is mapped at 32GB
> instead. The first 2 GB alias to the lower 2GB of DRAM mapped below 4GB,
> so we skip this part and map some more of the high DRAM, should anyone
> need it.
> 
> Signed-off-by: Andre Przywara <andre.przywara@arm.com>

Applied to u-boot/next, thanks!

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2022-04-03  0:16 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 16:30 [PATCH 00/11] vexpress64: OF_CONTROL and ARMv8-R64 support Andre Przywara
2022-03-04 16:30 ` [PATCH 01/11] vexpress64: fvp: Fix automatic boot Andre Przywara
2022-03-14 18:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 02/11] vexpress64: Kconfig: move board definitions out of arch/arm Andre Przywara
2022-04-03  0:13   ` Tom Rini
2022-03-04 16:30 ` [PATCH 03/11] arm: dts: Add Arm FVP Fastmodel RevC .dts files from Linux Andre Przywara
2022-04-03  0:13   ` Tom Rini
2022-03-04 16:30 ` [PATCH 04/11] vexpress64: fvp: enable OF_CONTROL Andre Przywara
2022-04-03  0:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 05/11] vexpress64: config header: unify environment definition Andre Przywara
2022-04-03  0:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 06/11] vexpress64: move hardware setting from defconfig to Kconfig Andre Przywara
2022-04-03  0:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 07/11] vexpress64: fvp: add distro_boot support Andre Przywara
2022-03-04 16:30 ` [PATCH 08/11] vexpress64: defconfigs: allow default commands Andre Przywara
2022-04-03  0:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 09/11] vexpress64: generalise page table generation Andre Przywara
2022-04-03  0:14   ` Tom Rini [this message]
2022-03-04 16:30 ` [PATCH 10/11] vexpress64: pick DRAM size from DT Andre Przywara
2022-04-03  0:14   ` Tom Rini
2022-03-04 16:30 ` [PATCH 11/11] vexpress64: Add ARMv8R-64 board variant Andre Przywara
2022-03-11 18:29   ` Liviu Dudau
2022-04-03  0:14   ` Tom Rini
2022-03-08  0:28 ` [PATCH 00/11] vexpress64: OF_CONTROL and ARMv8-R64 support Linus Walleij

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=20220403001426.GJ14476@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=andre.przywara@arm.com \
    --cc=linus.walleij@linaro.org \
    --cc=liviu.dudau@foss.arm.com \
    --cc=peter.hoyes@arm.com \
    --cc=sean.anderson@seco.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.