From: Kumar Gala <galak@kernel.crashing.org>
To: Madhulika Madishetty <mmadishetty@amcc.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/1 v3] AMCC PPC 460SX redwood SoC platform initial framework
Date: Wed, 4 Feb 2009 23:56:16 -0600 [thread overview]
Message-ID: <360B601C-FDC4-4F36-A716-6AD33FC0CD8B@kernel.crashing.org> (raw)
In-Reply-To: <AC5E1C3367E37D44970B81A6ADD1DA2C06D09DB5@SDCEXCHANGE01.ad.amcc.com>
On Feb 4, 2009, at 5:45 PM, Madhulika Madishetty wrote:
> diff --git a/arch/powerpc/kernel/cputable.c b/arch/powerpc/kernel/
> cputable.c
> index 923f87a..5c40da4 100644
> --- a/arch/powerpc/kernel/cputable.c
> +++ b/arch/powerpc/kernel/cputable.c
> @@ -43,6 +43,7 @@ extern void __setup_cpu_440spe(unsigned long
> offset, struct cpu_spec* spec);
> extern void __setup_cpu_440x5(unsigned long offset, struct cpu_spec*
> spec);
> extern void __setup_cpu_460ex(unsigned long offset, struct cpu_spec*
> spec);
> extern void __setup_cpu_460gt(unsigned long offset, struct cpu_spec*
> spec);
> +extern void __setup_cpu_460sx(unsigned long offset, struct cpu_spec
> *spec);
> extern void __setup_cpu_603(unsigned long offset, struct cpu_spec*
> spec);
> extern void __setup_cpu_604(unsigned long offset, struct cpu_spec*
> spec);
> extern void __setup_cpu_750(unsigned long offset, struct cpu_spec*
> spec);
> @@ -1634,6 +1635,18 @@ static struct cpu_spec __initdata cpu_specs[]
> = {
> .machine_check = machine_check_440A,
> .platform = "ppc440",
> },
> + { /* 460SX */
> + .pvr_mask = 0xffffff00,
> + .pvr_value = 0x13541800,
> + .cpu_name = "460SX",
> + .cpu_features = CPU_FTRS_44X,
> + .cpu_user_features = COMMON_USER_BOOKE,
> + .icache_bsize = 32,
> + .dcache_bsize = 32,
> + .cpu_setup = __setup_cpu_460sx,
> + .machine_check = machine_check_440A,
> + .platform = "ppc440",
> + },
This needs to be updated to include the new mmu_features field.
- k
prev parent reply other threads:[~2009-02-05 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 23:45 [PATCH 1/1 v3] AMCC PPC 460SX redwood SoC platform initial framework Madhulika Madishetty
2009-02-05 5:56 ` 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=360B601C-FDC4-4F36-A716-6AD33FC0CD8B@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mmadishetty@amcc.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