From: Bryan Wu <bryan.wu@canonical.com>
To: Tony Lindgren <tony@atomide.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, 09 Aug 2010 14:42:06 +0800 [thread overview]
Message-ID: <4C5FA33E.6020308@canonical.com> (raw)
In-Reply-To: <20100806070519.GB23778@atomide.com>
On 08/06/2010 03:05 PM, Tony Lindgren wrote:
> * Tony Lindgren <tony@atomide.com> [100806 09:55]:
>> * Kevin Hilman <khilman@deeprootsystems.com> [100806 01:48]:
>>>
>>>> Also with omap_4430sdp_defconfig, I see these compile errors
>>>> arch/arm/kernel/entry-armv.S: Assembler messages:
>>>> arch/arm/kernel/entry-armv.S:48: Error: bad instruction `test_for_ipi r0,r6,r5,lr'
>>>> arch/arm/kernel/entry-armv.S:48: Error: bad instruction `test_for_ipi r0,r6,r5,lr'
>>>> make[1]: *** [arch/arm/kernel/entry-armv.o] Error 1
>>>> make: *** [arch/arm/kernel] Error 2
>>>>
>>>> Doing a git log on entry-armv.S shows me a top commit which might
>>>> be an issue if conflicts are'nt resolved well.
>>>>
>>>> commit 7b70c4275f28702b76b273c8534c38f8313812e9
>>>> Merge: ceb0885... a20df56...
>>>> Author: Russell King <rmk+kernel@arm.linux.org.uk>
>>>> Date: Sat Jul 31 14:20:16 2010 +0100
>>>>
>>>> Merge branch 'devel-stable' into devel
>>>>
>>>> Conflicts:
>>>> arch/arm/kernel/entry-armv.S
>>>> arch/arm/kernel/setup.c
>>>> arch/arm/mm/init.c
>>>>
>>>> Maybe this is an issue in Tony's for-next as well. Haven't tested
>>>> it though.
>>>
>>> Yeah, I'm guessing this an issue in for-next, and probably l-o master
>>> too.
>>
>> Noticed that with omap3_defconfig with CONFIG_SMP enabled. Does the
>> following work for you?
>
> Here's a related patch that allows CONFIG_SMP to compile with
> omap3_defconfig. Booting still won't work before some arm generic
> code is changed.
>
> Regards,
>
> Tony
Tony,
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.
Thanks,
--
Bryan Wu <bryan.wu@canonical.com>
Kernel Developer +86.138-1617-6545 Mobile
Ubuntu Kernel Team | Hardware Enablement Team
Canonical Ltd. www.canonical.com
Ubuntu - Linux for human beings | www.ubuntu.com
next prev parent reply other threads:[~2010-08-09 6:42 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 ` Bryan Wu [this message]
2010-08-09 7:48 ` [PATCH] omap: Fix sev instruction usage for multi-omap Tony Lindgren
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=4C5FA33E.6020308@canonical.com \
--to=bryan.wu@canonical.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=rnayak@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.