From: Kumar Gala <kumar.gala@freescale.com>
To: Timur Tabi <timur@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/85xx: do not force PHYS_64BIT on Freescale reference boards
Date: Thu, 3 Nov 2011 15:40:44 -0500 [thread overview]
Message-ID: <379CBBC8-D3FA-44CB-9461-0AFB552956BE@freescale.com> (raw)
In-Reply-To: <4EB2E4F0.8040108@freescale.com>
On Nov 3, 2011, at 2:01 PM, Timur Tabi wrote:
> Kumar Gala wrote:
>> Nak. For certain boards like P204x-P50xx we only support a 36-bit =
address map.
>=20
> I understand that we don't supply a 32-bit U-boot or device tree, but =
is
> there any hard requirement that we force 36-bit kernels? If it's =
really a
> requirement, then adding to the Kconfig of each board doesn't sound =
like
> the best way to enforce this.
Yes, there is a requirement. Why would we allow you to build support =
for a board and not have it boot? The Kconfig is exactly how to enforce =
this.
- k=
prev parent reply other threads:[~2011-11-03 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 18:50 [PATCH] powerpc/85xx: do not force PHYS_64BIT on Freescale reference boards Timur Tabi
2011-11-03 18:58 ` Kumar Gala
2011-11-03 19:01 ` Timur Tabi
2011-11-03 20:40 ` Kumar Gala [this message]
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=379CBBC8-D3FA-44CB-9461-0AFB552956BE@freescale.com \
--to=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=timur@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