linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Albert Herranz <albert_herranz@yahoo.es>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [RFC PATCH v2 3/6] powerpc: broadway processor support
Date: Sat, 12 Dec 2009 08:59:52 +1100	[thread overview]
Message-ID: <1260568792.16132.362.camel@pasglop> (raw)
In-Reply-To: <1259880447-5008-4-git-send-email-albert_herranz@yahoo.es>

On Thu, 2009-12-03 at 23:47 +0100, Albert Herranz wrote:
> This patch extends the cputable entry of the 750CL to also match
> the 750CL-based "Broadway" cpu found on the Nintendo Wii.
> 
> As of this patch, the following "Broadway" design revision levels have
> been seen in the wild:
> - DD1.2 (87102)
> - DD2.0 (87200)
> 
> Signed-off-by: Albert Herranz <albert_herranz@yahoo.es>

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>


> ---
> v1 -> v2
> - Don't reorder the table. Suggestion by Grant Likely.
> 
>  arch/powerpc/kernel/cputable.c |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/cputable.c
> index 03c862b..2fc82ba 100644
> --- a/arch/powerpc/kernel/cputable.c
> +++ b/arch/powerpc/kernel/cputable.c
> @@ -697,9 +697,9 @@ static struct cpu_spec __initdata cpu_specs[] = {
>  		.machine_check		= machine_check_generic,
>  		.platform		= "ppc750",
>  	},
> -	{	/* 750CL */
> -		.pvr_mask		= 0xfffff0f0,
> -		.pvr_value		= 0x00087010,
> +	{	/* 750CL (and "Broadway") */
> +		.pvr_mask		= 0xfffff0e0,
> +		.pvr_value		= 0x00087000,
>  		.cpu_name		= "750CL",
>  		.cpu_features		= CPU_FTRS_750CL,
>  		.cpu_user_features	= COMMON_USER | PPC_FEATURE_PPC_LE,

  reply	other threads:[~2009-12-11 21:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 22:47 [RFC PATCH v2 0/6] powerpc: nintendo wii support Albert Herranz
2009-12-03 22:47 ` [RFC PATCH v2 1/6] powerpc: wii: device tree Albert Herranz
2009-12-04 15:25   ` Segher Boessenkool
2009-12-04 16:54     ` Albert Herranz
2009-12-11 21:59   ` Benjamin Herrenschmidt
2009-12-03 22:47 ` [RFC PATCH v2 2/6] powerpc: wii: bootwrapper bits Albert Herranz
2009-12-09 16:23   ` Segher Boessenkool
2009-12-11 21:59   ` Benjamin Herrenschmidt
2009-12-03 22:47 ` [RFC PATCH v2 3/6] powerpc: broadway processor support Albert Herranz
2009-12-11 21:59   ` Benjamin Herrenschmidt [this message]
2009-12-03 22:47 ` [RFC PATCH v2 4/6] powerpc: wii: hollywood interrupt controller support Albert Herranz
2009-12-11 22:01   ` Benjamin Herrenschmidt
2009-12-12 15:12   ` Segher Boessenkool
2009-12-03 22:47 ` [RFC PATCH v2 5/6] powerpc: wii: platform support Albert Herranz
2009-12-12 15:14   ` Segher Boessenkool
2009-12-03 22:47 ` [RFC PATCH v2 6/6] powerpc: wii: default config Albert Herranz
2009-12-11 22:02   ` Benjamin Herrenschmidt
2009-12-11 23:52 ` [RFC PATCH v2 0/6] powerpc: nintendo wii support Grant Likely
2009-12-12  0:18   ` Albert Herranz
2009-12-12  6:47     ` Grant Likely
2009-12-12  9:35       ` Albert Herranz

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=1260568792.16132.362.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=albert_herranz@yahoo.es \
    --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).