From: Shawn Guo <shawnguo@kernel.org>
To: Alistair Francis <alistair@alistair23.me>
Cc: arnd@arndb.de, olof@lixom.net, robh+dt@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, alistair23@gmail.com
Subject: Re: [PATCH v2 3/3] arch/arm/configs: Enable VMSPLIT_2G in imx_v6_v7_defconfig
Date: Fri, 29 Jan 2021 15:13:42 +0800 [thread overview]
Message-ID: <20210129071341.GH4356@dragon> (raw)
In-Reply-To: <20210117180301.1956-3-alistair@alistair23.me>
On Sun, Jan 17, 2021 at 10:03:01AM -0800, Alistair Francis wrote:
> The reMarkable2 requires VMSPLIT_2G, so lets set this in the
> imx_v6_v7_defconfig.
Hmm, why is VMSPLIT_2G required by reMarkable2?
Shawn
>
> Signed-off-by: Alistair Francis <alistair@alistair23.me>
> ---
> arch/arm/configs/imx_v6_v7_defconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm/configs/imx_v6_v7_defconfig b/arch/arm/configs/imx_v6_v7_defconfig
> index 55674cb1ffce..fa9229616106 100644
> --- a/arch/arm/configs/imx_v6_v7_defconfig
> +++ b/arch/arm/configs/imx_v6_v7_defconfig
> @@ -29,6 +29,7 @@ CONFIG_SOC_IMX7D=y
> CONFIG_SOC_IMX7ULP=y
> CONFIG_SOC_VF610=y
> CONFIG_SMP=y
> +CONFIG_VMSPLIT_2G=y
> CONFIG_ARM_PSCI=y
> CONFIG_HIGHMEM=y
> CONFIG_FORCE_MAX_ZONEORDER=14
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-01-29 7:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-17 18:02 [PATCH v2 1/3] imx7d-remarkable2.dts: Initial device tree for reMarkable2 Alistair Francis
2021-01-17 18:03 ` [PATCH v2 2/3] arch/arm/configs: Regenerate imx_v6_v7_defconfig Alistair Francis
2021-01-17 18:03 ` [PATCH v2 3/3] arch/arm/configs: Enable VMSPLIT_2G in imx_v6_v7_defconfig Alistair Francis
2021-01-29 7:13 ` Shawn Guo [this message]
2021-02-03 2:37 ` Alistair Francis
2021-02-03 7:50 ` Arnd Bergmann
2021-02-04 6:55 ` Alistair Francis
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=20210129071341.GH4356@dragon \
--to=shawnguo@kernel.org \
--cc=alistair23@gmail.com \
--cc=alistair@alistair23.me \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.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 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).