From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Li Yang-R58472 <r58472@freescale.com>
Subject: Re: [PATCH 1/2] powerpc/85xx: fix problem that prevents PHYS_64BIT from configurable
Date: Sat, 18 Feb 2012 08:10:33 +1100 [thread overview]
Message-ID: <1329513033.3980.1.camel@pasglop> (raw)
In-Reply-To: <CAOZdJXWQzxWXhU_4WmeKXx1mfTxGQx=-JZx0AkZcF7CmRrp1gQ@mail.gmail.com>
On Fri, 2012-02-17 at 16:22 +0000, Tabi Timur-B04825 wrote:
> Was this a Freescale internal decision, or is this a generic 85xx
> decision?
>
> For the record, I'm in favor in leaving out support for 32-bit address
> map in the upstream kernel, and having it be an option on the SDK
> only. However, in order to do that, we cannot have "select
> PHYS_64BIT" in the Kconfigs. It needs to be in the defconfigs
> instead. Putting it in the defconfig will eliminate the need to have
> it in every Kconfig block, so I think that's an improvement.
>
> Then the SDK can include a defconfig that does not have PHYS_64BIT
> defined. And the SDK can include 32-bit U-Boots and 32-bit device
> trees for any board where Freescale determines there is a need.
>
> I think Leo's patch simplifies things for everyone.
Sorry, I fail to see how... it basically makes all those boards
non-functional even when enabled...
What's wrong with the current scheme ?
Ben.
next prev parent reply other threads:[~2012-02-17 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-16 12:10 [PATCH 1/2] powerpc/85xx: fix problem that prevents PHYS_64BIT from configurable Li Yang
2012-02-16 12:10 ` [PATCH 2/2] powerpc/85xx: add a 36-bit corenet default config Li Yang
2012-02-16 15:56 ` [PATCH 1/2] powerpc/85xx: fix problem that prevents PHYS_64BIT from configurable Tabi Timur-B04825
2012-02-16 15:57 ` Tabi Timur-B04825
2012-02-17 1:27 ` Kumar Gala
2012-02-17 4:32 ` Li Yang-R58472
2012-02-17 8:43 ` Benjamin Herrenschmidt
2012-02-17 16:22 ` Tabi Timur-B04825
2012-02-17 21:10 ` Benjamin Herrenschmidt [this message]
2012-02-17 21:17 ` Timur Tabi
2012-02-17 23:01 ` Timur Tabi
2012-02-18 0:56 ` Scott Wood
2012-02-18 2:19 ` Benjamin Herrenschmidt
2012-02-20 20:30 ` Scott Wood
2012-02-17 8:42 ` Benjamin Herrenschmidt
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=1329513033.3980.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=B04825@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=r58472@freescale.com \
/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).