From: dwalker@codeaurora.org (Daniel Walker)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] arm: mm: do not set missing flags on ScorpionMP
Date: Wed, 28 Jul 2010 14:58:00 -0700 [thread overview]
Message-ID: <1280354280.21185.10.camel@c-dwalke-linux.qualcomm.com> (raw)
In-Reply-To: <20100724082334.GB15571@n2100.arm.linux.org.uk>
On Sat, 2010-07-24 at 09:23 +0100, Russell King - ARM Linux wrote:
> On Fri, Jul 23, 2010 at 11:58:02AM -0700, Jeff Ohlstein wrote:
> > From: Steve Muckle <smuckle@codeaurora.org>
> >
> > ScorpionMP does not have the SMP/nAMP mode and TLB ops
> > broadcasting bits in the ACTLR.
>
> Please provide a separate instance of __v7_proc_info for your processor
> and direct it to jump into the __v7_setup code after this setup instead.
You mean add another label into __v7_setup along with a proc-msm.S to
jump over this code?
Daniel
--
Sent by an consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2010-07-28 21:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 18:58 [PATCH 0/3] ARM changes for ScorpionMP support Jeff Ohlstein
2010-07-23 18:58 ` [PATCH 1/3] arm: Kconfig option for ARCH_MSM_SCORPIONMP Jeff Ohlstein
2010-07-23 18:58 ` [PATCH 2/3] arm: mm: do not set missing flags on ScorpionMP Jeff Ohlstein
2010-07-24 8:23 ` Russell King - ARM Linux
2010-07-28 21:58 ` Daniel Walker [this message]
2010-07-28 22:36 ` Russell King - ARM Linux
2010-07-28 22:51 ` Daniel Walker
2010-07-29 7:18 ` Russell King - ARM Linux
2010-07-29 22:42 ` Daniel Walker
2010-07-30 7:19 ` Russell King - ARM Linux
2010-07-30 17:09 ` Daniel Walker
2010-07-30 20:20 ` Russell King - ARM Linux
2010-07-30 20:46 ` Daniel Walker
2010-07-23 18:58 ` [PATCH 3/3] arm: macros for wfe, sev instructions Jeff Ohlstein
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=1280354280.21185.10.camel@c-dwalke-linux.qualcomm.com \
--to=dwalker@codeaurora.org \
--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).