From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: question about ARM11MP cpu architecture identification
Date: Tue, 12 Jan 2010 18:01:27 +0000 [thread overview]
Message-ID: <1263319287.29654.112.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20100112172422.GD5633@n2100.arm.linux.org.uk>
On Tue, 2010-01-12 at 17:24 +0000, Russell King - ARM Linux wrote:
> On Tue, Jan 12, 2010 at 05:17:33PM +0000, Russell King - ARM Linux wrote:
> > On Tue, Jan 12, 2010 at 07:03:35PM +0200, saeed bishara wrote:
> > > On Tue, Jan 12, 2010 at 6:55 PM, Catalin Marinas
> > > <catalin.marinas@arm.com> wrote:
> > > > On Tue, 2010-01-12 at 16:42 +0000, Russell King - ARM Linux wrote:
> > > >> On Tue, Jan 12, 2010 at 04:26:12PM +0000, Catalin Marinas wrote:
> > > >> > On Tue, 2010-01-12 at 16:21 +0000, saeed bishara wrote:
> > > >> > > The ARM11MP (rev r2p0) cpu architecture is ARMv6, and according to
> > > >> > > the http://infocenter.arm.com, its Main ID register is 0x410FB024, and
> > > >> > > the MMFR[3:0] is 3. but it looks to me that the cpu_architecture()
> > > >> > > will identify it as ARMv7, and if the kernel was configured with
> > > >> > > CPU_V7 only, then the lookup_processor_type() function also will
> > > >> > > identify it as ARMv7. Am I missing something here?
> > > >> >
> > > >> > cpu_architecture() returns the architecture version of the supported MMU
> > > >> > which on ARM11MPCore is the same as on ARMv7.
> > > >> >
> > > >> > Even if it is possible to configure both v6 and v7 in the same kernel, I
> > > >> > don't think it is currently possible to successfully run such kernel.
> > > >>
> > > >> What makes you think that? I've been building v6+v7 kernels for Realview
> > > >> (with a patch to provide the right build options for the ARMv7 arch/arm/mm
> > > >> files) and ISTR it works fine on my Realview board.
> > > >
> > > > I don't remember exactly but it didn't work for me some time ago. I
> > > > think it failed to build (though I could have worked around this with
> > > > something like -march=all).
> > > >
> > > I think you need the attached patch from Lennert (it was planned to be
> > > sent later by me)
> >
> > Using -Wa,-march= for assembler options is actually a better idea.
> > I'll update my patch with that (which actually reflects what I did
> > for Integrator/CP with ARM926 + v6).
>
> Ok, here's the combined patch. Ack?
Looks fine to me. Thanks.
--
Catalin
next prev parent reply other threads:[~2010-01-12 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 16:21 question about ARM11MP cpu architecture identification saeed bishara
2010-01-12 16:26 ` Catalin Marinas
2010-01-12 16:42 ` Russell King - ARM Linux
2010-01-12 16:55 ` Catalin Marinas
2010-01-12 17:03 ` saeed bishara
2010-01-12 17:17 ` Russell King - ARM Linux
2010-01-12 17:24 ` Russell King - ARM Linux
2010-01-12 18:01 ` Catalin Marinas [this message]
2010-01-12 19:55 ` Nicolas Pitre
2010-01-13 11:27 ` saeed bishara
2010-01-13 11:36 ` Russell King - ARM Linux
2010-01-12 17:06 ` Russell King - ARM Linux
2010-01-12 16:50 ` saeed bishara
2010-01-12 16:34 ` Russell King - ARM Linux
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=1263319287.29654.112.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm.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).