From: Kevin Hilman <khilman@linaro.org>
To: Kukjin Kim <kgene@kernel.org>
Cc: 'Olof Johansson' <olof@lixom.net>,
linux-samsung-soc@vger.kernel.org,
'Mark Brown' <broonie@kernel.org>,
linux-arm-kernel@lists.infradead.org,
'Arnd Bergmann' <arnd@arndb.de>
Subject: Re: Broken device trees for exynos in linux-next
Date: Mon, 19 Aug 2013 08:15:35 -0700 [thread overview]
Message-ID: <8738q5lnjc.fsf@kernel.org> (raw)
In-Reply-To: <159201ce9b36$2a513f30$7ef3bd90$@org> (Kukjin Kim's message of "Sat, 17 Aug 2013 19:40:18 +0900")
Kukjin Kim <kgene@kernel.org> writes:
[...]
> If we could make LPAE enabled defconfig for all ARM platforms, I'm fine. I
> think your concern is creating SoC specific defconfig and I agree with you.
> But I'm not sure how we can support LPAE enabled defconfig for ARM
> platforms.
Here's a simple way to keep a single base defconfig, and enable LPAE:
$ echo CONFIG_ARM_LPAE=y > /tmp/lpae.config
$ ./scripts/kconfig/merge_config.sh arch/arm/config/exynos_defconfig /tmp/lpae.config
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: Broken device trees for exynos in linux-next
Date: Mon, 19 Aug 2013 08:15:35 -0700 [thread overview]
Message-ID: <8738q5lnjc.fsf@kernel.org> (raw)
In-Reply-To: <159201ce9b36$2a513f30$7ef3bd90$@org> (Kukjin Kim's message of "Sat, 17 Aug 2013 19:40:18 +0900")
Kukjin Kim <kgene@kernel.org> writes:
[...]
> If we could make LPAE enabled defconfig for all ARM platforms, I'm fine. I
> think your concern is creating SoC specific defconfig and I agree with you.
> But I'm not sure how we can support LPAE enabled defconfig for ARM
> platforms.
Here's a simple way to keep a single base defconfig, and enable LPAE:
$ echo CONFIG_ARM_LPAE=y > /tmp/lpae.config
$ ./scripts/kconfig/merge_config.sh arch/arm/config/exynos_defconfig /tmp/lpae.config
Kevin
next prev parent reply other threads:[~2013-08-19 15:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 16:43 Broken device trees for exynos in linux-next Olof Johansson
2013-08-15 16:43 ` Olof Johansson
2013-08-16 0:04 ` Kukjin Kim
2013-08-16 0:04 ` Kukjin Kim
2013-08-16 0:35 ` Mark Brown
2013-08-16 0:35 ` Mark Brown
2013-08-16 0:42 ` Mark Brown
2013-08-16 0:42 ` Mark Brown
2013-08-16 3:34 ` Padma Venkat
2013-08-16 3:34 ` Padma Venkat
2013-08-16 16:04 ` Olof Johansson
2013-08-16 16:04 ` Olof Johansson
2013-08-16 18:03 ` Mark Brown
2013-08-16 18:03 ` Mark Brown
2013-08-17 10:40 ` Kukjin Kim
2013-08-17 10:40 ` Kukjin Kim
2013-08-19 15:15 ` Kevin Hilman [this message]
2013-08-19 15:15 ` Kevin Hilman
2013-08-22 9:55 ` Kukjin Kim
2013-08-22 9:55 ` Kukjin Kim
2013-08-22 16:20 ` Olof Johansson
2013-08-22 16:20 ` Olof Johansson
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=8738q5lnjc.fsf@kernel.org \
--to=khilman@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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.