From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: realview compulsory enables CONFIG_ARM_PATCH_PHYS_VIRT on me
Date: Mon, 05 Dec 2011 15:57:50 -0600 [thread overview]
Message-ID: <4EDD3E5E.6050106@gmail.com> (raw)
In-Reply-To: <CACRpkdZ8jpz7WTP3gpfcTykQZaCjQLN9PZCAS+UJOWrzZo1bjQ@mail.gmail.com>
On 12/05/2011 03:22 PM, Linus Walleij wrote:
> Hi Nico,
>
> now I'm lost, I discussed by boot problems on ARM PB1176
> with Marc and after some investigation I found this strange thing on
> the lastest rc:s since -rc1:
>
> In arch/arm/Kconfig ARM_PATCH_PHYS_VIRT is forcibly
> disabled like so:
>
> depends on !ARCH_REALVIEW || !SPARSEMEM
should be !ARCH_REALVIEW && !SPARSEMEM ?
Rob
>
> However if I just configure it for the realview_defconfig:
>
> mkdir foo
> make -f Makefile ARCH=arm CROSS_COMPILE=arm-none-eabi-
> KBUILD_OUTPUT=foo realview_defconfig
>
> It strangely selects this anyway, because now foo/.config has:
> CONFIG_ARM_PATCH_PHYS_VIRT=y
>
> Kconfig is a djungle to me, but I simply cannot find out
> what is setting this anyway. The problem is not there on
> v3.1, it does not get selected.
>
> Any hints?
>
> Yours,
> Linus Walleij
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2011-12-05 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 21:22 realview compulsory enables CONFIG_ARM_PATCH_PHYS_VIRT on me Linus Walleij
2011-12-05 21:57 ` Rob Herring [this message]
2011-12-05 22:08 ` Nicolas Pitre
2011-12-05 23:36 ` Russell King - ARM Linux
2011-12-06 0:37 ` Nicolas Pitre
2011-12-06 0:46 ` Russell King - ARM Linux
2011-12-06 8:29 ` Colin Tuckley
2011-12-06 10:30 ` 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=4EDD3E5E.6050106@gmail.com \
--to=robherring2@gmail.com \
--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 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.