linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Anatolij Gustschin <agust@denx.de>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: fix PHYS_64BIT selection for P1022DS
Date: Mon, 26 Sep 2011 17:14:25 -0500	[thread overview]
Message-ID: <4E80F941.2090408@freescale.com> (raw)
In-Reply-To: <FAF4E48A-0966-4A6E-8D31-B30D07CB0746@kernel.crashing.org>

Kumar Gala wrote:
> Why, the way this patch makes it will work both with a 32-bit or 36-bit address map.   The comment should be fixed since its wrong.

I think the BSP team had said that there is a significant performance
improvement in some benchmark when 36-bit support is disabled.  That's why they
like to keep 32-bit and 36-bit environments for both, and why they default to
32-bit.

-- 
Timur Tabi
Linux kernel developer at Freescale

  reply	other threads:[~2011-09-26 22:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-23 19:32 [PATCH] powerpc/85xx: fix PHYS_64BIT selection for P1022DS Anatolij Gustschin
2011-09-25 17:06 ` Tabi Timur-B04825
2011-09-26 22:12   ` Kumar Gala
2011-09-26 22:14     ` Timur Tabi [this message]
2011-09-26 22:24     ` Scott Wood
2011-10-12  4:53 ` Kumar Gala
2011-10-13 14:14   ` Tabi Timur-B04825
2011-10-13 15:31     ` Kumar Gala
2011-10-13 15:35       ` Timur Tabi
2011-10-13 15:41         ` Kumar Gala
2011-10-13 15:45           ` Timur Tabi
2011-10-13 15:52             ` Anatolij Gustschin
2011-10-13 15:50         ` Anatolij Gustschin
2011-10-13 15:59           ` Timur Tabi

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=4E80F941.2090408@freescale.com \
    --to=timur@freescale.com \
    --cc=agust@denx.de \
    --cc=galak@kernel.crashing.org \
    --cc=linuxppc-dev@lists.ozlabs.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 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).