From: Daniel Walker <danielwa@cisco.com>
To: Kumar Gala <galak@kernel.crashing.org>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
linuxppc-dev@lists.ozlabs.org,
devicetree-discuss@lists.ozlabs.org,
"polaris-kernel-dev(mailer list)" <polaris-kernel-dev@cisco.com>
Subject: Freescale old style SMP
Date: Mon, 8 Feb 2016 13:57:08 -0800 [thread overview]
Message-ID: <56B90F34.1060802@cisco.com> (raw)
In this patch,
http://repository.timesys.com/buildsources/k/kernel/kernel-2.6.32/2.6.32-fsl-p1022ds-201003260230.patch
The SMP code is different from what's upstream. It looks like Freescale
may have changed the way SMP info is passed from the bootloader to the
kernel.
Unfortunately, Cisco release a product with a bootloader which conforms
to what's in the patch above. Newer kernels don't initialize smp using
our bootloader.
I'm wondering if maybe I'm missing something here, and the smp
initialization is actually the same, or if there's some fall back which
is compatible? If not, then what's the best way to integrate this old
method into what's already upstream?
Thanks,
Daniel
reply other threads:[~2016-02-08 22:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=56B90F34.1060802@cisco.com \
--to=danielwa@cisco.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=galak@kernel.crashing.org \
--cc=grant.likely@linaro.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=polaris-kernel-dev@cisco.com \
--cc=rob.herring@calxeda.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;
as well as URLs for NNTP newsgroup(s).