From: Tony Lindgren <tony@atomide.com>
To: Bryan Wu <bryan.wu@canonical.com>
Cc: Kevin Hilman <khilman@deeprootsystems.com>,
"Nayak, Rajendra" <rnayak@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap: Fix sev instruction usage for multi-omap
Date: Mon, 9 Aug 2010 10:48:47 +0300 [thread overview]
Message-ID: <20100809074846.GC32480@atomide.com> (raw)
In-Reply-To: <4C5FA33E.6020308@canonical.com>
* Bryan Wu <bryan.wu@canonical.com> [100809 09:35]:
>
> I also did similar thing these days. And yes, with these 2 CONFIG_SMP related
> patches in omap3_defconfig, I can built a single for omap2/3/4 with CONFIG_SMP=y.
>
> But the kernel still doesn't boot on both omap3 beagle board and omap4 panda
> board on my side.
>
> I'm very glad to help this out.
Yeah let's try to figure out what needs to be done to boot it. To me it
looks like we should be able to get omap3 & 4 kernel working with CONFIG_SMP
with (hopefully) minor changes.
Then getting omap2 working will require more work as some instructions
require CONFIG_CPU_32v6K extensions, and 24xx does not support that.
Regards,
Tony
prev parent reply other threads:[~2010-08-09 7:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 22:50 PM branch updated to v2.6.35, SRF dropped Kevin Hilman
2010-08-04 23:25 ` Nishanth Menon
2010-08-05 22:29 ` Kevin Hilman
2010-08-05 23:11 ` Nishanth Menon
2010-08-05 14:21 ` Nayak, Rajendra
2010-08-05 22:45 ` Kevin Hilman
2010-08-06 7:03 ` [PATCH] omap: Use CONFIG_SMP for test_for_ipi and test_for_ltirq belong (Re: PM branch updated to v2.6.35, SRF dropped) Tony Lindgren
2010-08-06 7:05 ` [PATCH] omap: Fix sev instruction usage for multi-omap Tony Lindgren
2010-08-06 11:29 ` Nayak, Rajendra
2010-08-06 11:50 ` [PATCH] omap: Fix omap_4430sdp_defconfig for make oldconfig Tony Lindgren
2010-08-06 13:12 ` Nayak, Rajendra
2010-08-09 6:42 ` [PATCH] omap: Fix sev instruction usage for multi-omap Bryan Wu
2010-08-09 7:48 ` Tony Lindgren [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=20100809074846.GC32480@atomide.com \
--to=tony@atomide.com \
--cc=bryan.wu@canonical.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.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).