From: haojian.zhuang@gmail.com (Haojian Zhuang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: add base support for Marvell Dove SoC
Date: Fri, 4 Dec 2009 00:41:48 -0500 [thread overview]
Message-ID: <771cded00912032141x368ae423n6603edbd7acd3f10@mail.gmail.com> (raw)
In-Reply-To: <1259084033-7283-2-git-send-email-saeed@marvell.com>
> diff --git a/arch/arm/mm/proc-v6.S b/arch/arm/mm/proc-v6.S
> index 70f75d2..ebfe6c1 100644
> --- a/arch/arm/mm/proc-v6.S
> +++ b/arch/arm/mm/proc-v6.S
> @@ -130,9 +130,16 @@ ENTRY(cpu_v6_set_pte_ext)
>
>
>
> -
> + ? ? ? .type ? cpu_v6_name, #object
> ?cpu_v6_name:
> ? ? ? ?.asciz ?"ARMv6-compatible processor"
> + ? ? ? .size ? cpu_v6_name, . - cpu_v6_name
> +
> + ? ? ? .type ? cpu_pj4_name, #object
> +cpu_pj4_name:
> + ? ? ? .asciz ?"Marvell PJ4 processor"
> + ? ? ? .size ? cpu_pj4_name, . - cpu_pj4_name
> +
> ? ? ? ?.align
>
> ? ? ? ?__INIT
> @@ -241,3 +248,27 @@ __v6_proc_info:
> ? ? ? ?.long ? v6_user_fns
> ? ? ? ?.long ? v6_cache_fns
> ? ? ? ?.size ? __v6_proc_info, . - __v6_proc_info
> +
> + ? ? ? .type ? __pj4_v6_proc_info, #object
> +__pj4_v6_proc_info:
> + ? ? ? .long ? 0x560f5810
> + ? ? ? .long ? 0xff0ffff0
> + ? ? ? .long ? PMD_TYPE_SECT | \
> + ? ? ? ? ? ? ? PMD_SECT_BUFFERABLE | \
> + ? ? ? ? ? ? ? PMD_SECT_CACHEABLE | \
These two flags are different from flags used in v6 proc_info. Is PJ4
full compatible to armv6? Is there any reason to select
PMD_SECT_BUFFERABLE & PMD_SECT_CACHEABLE at here?
> + ? ? ? ? ? ? ? PMD_SECT_AP_WRITE | \
> + ? ? ? ? ? ? ? PMD_SECT_AP_READ
> + ? ? ? .long ? PMD_TYPE_SECT | \
> + ? ? ? ? ? ? ? PMD_SECT_XN | \
> + ? ? ? ? ? ? ? PMD_SECT_AP_WRITE | \
> + ? ? ? ? ? ? ? PMD_SECT_AP_READ
> + ? ? ? b ? ? ? __v6_setup
> + ? ? ? .long ? cpu_arch_name
> + ? ? ? .long ? cpu_elf_name
> + ? ? ? .long ? HWCAP_SWP|HWCAP_HALF|HWCAP_THUMB|HWCAP_FAST_MULT|HWCAP_EDSP
> + ? ? ? .long ? cpu_pj4_name
> + ? ? ? .long ? v6_processor_functions
> + ? ? ? .long ? v6wbi_tlb_fns
> + ? ? ? .long ? v6_user_fns
> + ? ? ? .long ? v6_cache_fns
> + ? ? ? .size ? __v6_proc_info, . - __v6_proc_info
You created __pj4_v6_proc_info. But you still used __v6_proc_info at here. Why?
next prev parent reply other threads:[~2009-12-04 5:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 17:33 [PATCH 0/3] add support for Marvell's Dove SoC Saeed Bishara
2009-11-24 17:33 ` [PATCH 1/3] ARM: add base support for Marvell " Saeed Bishara
2009-11-24 17:33 ` [PATCH 2/3] Add Tauros2 L2 cache controller support Saeed Bishara
2009-11-24 17:33 ` [PATCH 3/3] rtc: add support for Dove soc to the rtc-mv driver Saeed Bishara
2009-11-24 22:28 ` [PATCH 1/3] ARM: add base support for Marvell Dove SoC Saeed Bishara
2009-11-27 20:05 ` Russell King - ARM Linux
2009-11-27 20:48 ` Nicolas Pitre
2009-11-28 8:04 ` saeed bishara
2009-11-28 16:41 ` Nicolas Pitre
2009-11-28 18:09 ` Russell King - ARM Linux
2009-11-28 19:03 ` Nicolas Pitre
2009-12-01 9:57 ` Russell King - ARM Linux
2009-12-01 10:10 ` Saeed Bishara
2009-12-04 5:41 ` Haojian Zhuang [this message]
2009-12-04 17:37 ` Nicolas Pitre
2009-12-06 12:44 ` saeed bishara
2009-12-06 15:42 ` Nicolas Pitre
2009-12-06 16:13 ` saeed bishara
2009-12-06 17:23 ` Russell King - ARM Linux
2009-12-07 1:35 ` Nicolas Pitre
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=771cded00912032141x368ae423n6603edbd7acd3f10@mail.gmail.com \
--to=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).