linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH] powerpc: Fix PowerPC 750CL CPU features
Date: Thu, 12 Apr 2007 18:41:29 +0200	[thread overview]
Message-ID: <aeef7937e978aec33074251c48dca389@kernel.crashing.org> (raw)
In-Reply-To: <1176382146.6379.28.camel@zod.rchland.ibm.com>

> PowerPC 750CL has high BATs.  The patch below sets cpu_features to 
> match that.
> Without it, the original firmware mappings in the high BATs aren't 
> cleared
> which can cause "odd" address translations to occur.

> -		.cpu_features		= CPU_FTRS_750,
> +		.cpu_features		= CPU_FTRS_750GX,

The difference between these two is

#define CPU_FTRS_750GX  (CPU_FTR_DUAL_PLL_750FX | CPU_FTR_HAS_HIGH_BATS)
#define CPU_FTRS_750    (CPU_FTR_COMMON)

750GX excludes COMMON, which seems like a bug.  With
your change, 750CL uses DUAL_PLL_750FX; does it actually
have that feature?

Either way, it seems a good idea to create a CPU_FTRS_750CL,
the CL is an evolution of the CX, not the FX/GX (in name
at least, dunno about the gory details).

> -		.cpu_setup		= __setup_cpu_750cx,
> +		.cpu_setup		= __setup_cpu_750fx,

Same thing here.  Are you sure 750CL doesn't need
the NAP workaround?  [Is anyone sure the 750CX
actually needs it -- the comment in cpu_setup_6xx.S
doesn't instill much confidence.]


Segher

  parent reply	other threads:[~2007-04-12 16:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-12 12:49 [PATCH] powerpc: Fix PowerPC 750CL CPU features Josh Boyer
2007-04-12 13:49 ` Milton Miller
2007-04-12 13:53   ` Josh Boyer
2007-04-12 16:41 ` Segher Boessenkool [this message]
2007-04-12 17:06   ` Kumar Gala
2007-04-12 17:11     ` Josh Boyer
2007-04-12 17:10   ` Josh Boyer
2007-04-12 19:24     ` Segher Boessenkool
2007-04-13  2:28   ` Benjamin Herrenschmidt
2007-04-13 10:52     ` Josh Boyer

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=aeef7937e978aec33074251c48dca389@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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).