From: Tabi Timur-B04825 <B04825@freescale.com>
To: Li Yang-R58472 <r58472@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
Huang Changming-R66093 <r66093@freescale.com>,
Wood Scott-B07421 <B07421@freescale.com>
Subject: Re: [PATCH] powerpc/85xx: allow CONFIG_PHYS_64BIT to be selectable
Date: Fri, 24 Feb 2012 03:50:42 +0000 [thread overview]
Message-ID: <4F470910.9080008@freescale.com> (raw)
In-Reply-To: <94F013E7935FF44C83EBE7784D62AD3F0578D305@039-SN2MPN1-023.039d.mgd.msft.net>
Li Yang-R58472 wrote:
> The mpc85xx_defconfig does include silicons with e500v1 core which
> doesn't have the 36-bit support. Won't enabling 36-bit support by
> default break the support for them?
No. The kernel will detect at runtime that that it's an e500v1 core and=20
it won't try to create 36-bit TLBs. (e.g. it won't write to MAS7).
Please remember that the Kconfig for the P1022DS already forced PHYS_64BIT=
=20
for all mpc85xx platforms. All we're doing is making it possible to=20
deselect PHYS_64BIT.
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2012-02-24 3:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 19:53 [PATCH] powerpc/85xx: allow CONFIG_PHYS_64BIT to be selectable Timur Tabi
2012-02-23 6:25 ` Huang Changming-R66093
2012-02-23 12:24 ` Tabi Timur-B04825
2012-02-24 1:54 ` Huang Changming-R66093
2012-02-24 2:29 ` Li Yang-R58472
2012-02-24 2:45 ` Tabi Timur-B04825
2012-02-24 2:59 ` Li Yang-R58472
2012-02-24 3:01 ` Huang Changming-R66093
2012-02-24 3:04 ` Tabi Timur-B04825
2012-02-24 3:24 ` Huang Changming-R66093
2012-02-24 3:36 ` Tabi Timur-B04825
2012-02-24 3:40 ` Li Yang-R58472
2012-02-24 3:50 ` Tabi Timur-B04825 [this message]
2012-02-24 4:02 ` Li Yang-R58472
2012-02-24 4:11 ` Tabi Timur-B04825
2012-03-16 20:01 ` Kumar Gala
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=4F470910.9080008@freescale.com \
--to=b04825@freescale.com \
--cc=B07421@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=r58472@freescale.com \
--cc=r66093@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 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.