From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: RE: [PATCH 1/2] powerpc/85xx: fix problem that prevents PHYS_64BIT from configurable
Date: Fri, 17 Feb 2012 19:43:31 +1100 [thread overview]
Message-ID: <1329468211.2892.61.camel@pasglop> (raw)
In-Reply-To: <94F013E7935FF44C83EBE7784D62AD3F057427B6@039-SN2MPN1-023.039d.mgd.msft.net>
On Fri, 2012-02-17 at 04:32 +0000, Li Yang-R58472 wrote:
> >Additionally, outside of maybe P2041RDB I believe the majority of
> these
> >boards ship with 4G of DDR (but that off the top of my head) and thus
> >require the 36-bit / PHYS_64BIT support to be enabled.
>
> I know that current support of DPAA boards requires 36-bit. But I
> don't think they need to select the PHYS_64BIT option directly and
> make it not configurable. It's conflicting with the logic that
> enabling a platform support doesn't mean the kernel is only running on
> that platform. Btw: what's your recommendations on solving this?
But selecting PHYS_64BIT shouldn't prevent running on the other
platforms. If it does, then this needs to be fixed.
Cheers,
Ben.
next prev parent reply other threads:[~2012-02-17 8:43 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 [this message]
2012-02-17 16:22 ` Tabi Timur-B04825
2012-02-17 21:10 ` Benjamin Herrenschmidt
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=1329468211.2892.61.camel@pasglop \
--to=benh@kernel.crashing.org \
--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).