linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kgene@kernel.org (Kukjin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: Broken device trees for exynos in linux-next
Date: Thu, 22 Aug 2013 18:55:35 +0900	[thread overview]
Message-ID: <1c7e01ce9f1d$bf4967d0$3ddc3770$@org> (raw)
In-Reply-To: <8738q5lnjc.fsf@kernel.org>

Kevin Hilman wrote:
> 
> 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
> 
Yeah, it can be used for test. But there are many differences between
exynos_defconfig and exynos5440_defconfig...PCIe, GbE, HugeTLB and KVM...so
I'm still wondering how to handle it without other defconfig.

Olof, do you still having objection for exynos5440_defconfig? If so, OK I
will revert exynos5440_defconfig for now so that I could pull out the
'defconfig' branch to arm-soc for upcoming merge window. Then, let's discuss
again :)

Thanks,
Kukjin

  reply	other threads:[~2013-08-22  9:55 UTC|newest]

Thread overview: 11+ 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-16  0:04 ` Kukjin Kim
2013-08-16  0:35   ` Mark Brown
2013-08-16  0:42     ` Mark Brown
2013-08-16  3:34       ` Padma Venkat
2013-08-16 16:04   ` Olof Johansson
2013-08-16 18:03     ` Mark Brown
2013-08-17 10:40     ` Kukjin Kim
2013-08-19 15:15       ` Kevin Hilman
2013-08-22  9:55         ` Kukjin Kim [this message]
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='1c7e01ce9f1d$bf4967d0$3ddc3770$@org' \
    --to=kgene@kernel.org \
    --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).